Re: [NTG-context] Getting Textadept to open pdf?

2021-09-26 Thread Jairo A. del Rio via ntg-context 
El dom, 26 de sep. de 2021 a la(s) 22:29, jbf (roma83...@gmail.com)
escribió:

> Hmm. I'm not using evince (could, I suppose) but I see that in the file
> you mention there is already:
>
> ['okular']= [[okular --unique "%filename%"]], and I have already
> adapted the init.lua file in /.texadept to use okular rather than sumatra,
> with textadept.run.compile_commands.tex =
> '/home/me/bin/context/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
> context --autopdf=okular "%f"'
>
> So, following your logic, I should then only need to add, further on,
> pdfview.method = "okular", which I have done, but still no joy.
>
> In such a case, you only need to comment on the second option, i. e.
Sumatra:

--The last one wins
pdfview.method = "okular"
--pdfview.method = "sumatra" -- faster and more complete

I haven't edited textadept settings btw, so it works for me with --autopdf
alone.

> Julian
>
>
> On 27/9/21 1:06 pm, Jairo A. del Rio wrote:
>
> Hi. Maybe there's an easier way to do it without changing any file or via
> mtxrun's command line, but the following is what I do:
>
> In l-pdfview.lua (mkiv folder, lines from 38) PDF view options are
> available. I've added
>
> ['evince']= [[evince "%filename%"]] -- My favorite viewer
>
> And then, after pdfview.method assignments,
>
> pdfview.method = "evince"
>
> Now textadept opens the .tex file once compiled. I don't know if making
> the format again is mandatory, but it doesn't hurt, anyways. I hope this
> helps.
> Best regards,
>
> Jairo
>
>
>
> El dom, 26 de sep. de 2021 a la(s) 20:54, jbf via ntg-context (
> ntg-context@ntg.nl) escribió:
>
>> The occasional response to a similar question can be found, e.g. on
>> stackexchange, but none of the responses work for me.
>>
>> Textadept is very fast at compiling (and does compile correctly). I can
>> certainly open the pdf independently in various pdf viewers, but I
>> cannot get Textadept to automatically open, say, Okular (installed on
>> Linux Mint), at the end of the process.
>>
>> The last part of the log reads:
>>
>> mkiv lua stats  > runtime: 0.640 seconds, 8 processed pages, 8 shipped
>> pages, 12.492 pages/second
>> mtx-context | pdfview methods: auto default okular pdfxcview
>> sumatra, current method: okular (directives_pdfview_method)
>> pdfview | command: okular --unique "test1.pdf" 1>/dev/null
>> 2>/dev/null &
>> mtx-context | pdfview overhead: 0.001 seconds
>> system  | total runtime: 0.649 seconds of 0.701 seconds
>>
>>  > exit status: 0
>>
>> Have tried setting up a custom text editor on okular with:
>> /home/me/.textadept "%f" -e textadept.editing.goto_line(%l-1), as
>> suggested by one response, but to no avail. Current version of ConTeXt
>> is 2021.09.17 10:01
>>
>> Anyone tried Textadept successfully and might have a suggestion?
>>
>> Julian
>>
>>
>> ___
>> 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
>>
>> ___
>>
>
___
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] Getting Textadept to open pdf?

2021-09-26 Thread jbf via ntg-context 
Hmm. I'm not using evince (could, I suppose) but I see that in the file 
you mention there is already:


['okular']    = [[okular --unique "%filename%"]], and I have already 
adapted the init.lua file in /.texadept to use okular rather than 
sumatra, with textadept.run.compile_commands.tex = 
'/home/me/bin/context/tex/texmf-linux-64/bin/mtxrun --autogenerate 
--script context --autopdf=okular "%f"'


So, following your logic, I should then only need to add, further on, 
pdfview.method = "okular", which I have done, but still no joy.


Julian


On 27/9/21 1:06 pm, Jairo A. del Rio wrote:
Hi. Maybe there's an easier way to do it without changing any file or 
via mtxrun's command line, but the following is what I do:


In l-pdfview.lua (mkiv folder, lines from 38) PDF view options are 
available. I've added


['evince']    = [[evince "%filename%"]] -- My favorite viewer

And then, after pdfview.method assignments,

pdfview.method = "evince"

Now textadept opens the .tex file once compiled. I don't know if 
making the format again is mandatory, but it doesn't hurt, anyways. I 
hope this helps.

Best regards,

Jairo



El dom, 26 de sep. de 2021 a la(s) 20:54, jbf via ntg-context 
(ntg-context@ntg.nl ) escribió:


The occasional response to a similar question can be found, e.g. on
stackexchange, but none of the responses work for me.

Textadept is very fast at compiling (and does compile correctly).
I can
certainly open the pdf independently in various pdf viewers, but I
cannot get Textadept to automatically open, say, Okular (installed on
Linux Mint), at the end of the process.

The last part of the log reads:

mkiv lua stats  > runtime: 0.640 seconds, 8 processed pages, 8
shipped
pages, 12.492 pages/second
mtx-context | pdfview methods: auto default okular pdfxcview
sumatra, current method: okular (directives_pdfview_method)
pdfview | command: okular --unique "test1.pdf" 1>/dev/null
2>/dev/null &
mtx-context | pdfview overhead: 0.001 seconds
system  | total runtime: 0.649 seconds of 0.701 seconds

 > exit status: 0

Have tried setting up a custom text editor on okular with:
/home/me/.textadept "%f" -e textadept.editing.goto_line(%l-1), as
suggested by one response, but to no avail. Current version of
ConTeXt
is 2021.09.17 10:01

Anyone tried Textadept successfully and might have a suggestion?

Julian


___
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 

___

___
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] Getting Textadept to open pdf?

2021-09-26 Thread Jairo A. del Rio via ntg-context 
Hi. Maybe there's an easier way to do it without changing any file or via
mtxrun's command line, but the following is what I do:

In l-pdfview.lua (mkiv folder, lines from 38) PDF view options are
available. I've added

['evince']= [[evince "%filename%"]] -- My favorite viewer

And then, after pdfview.method assignments,

pdfview.method = "evince"

Now textadept opens the .tex file once compiled. I don't know if making the
format again is mandatory, but it doesn't hurt, anyways. I hope this helps.
Best regards,

Jairo



El dom, 26 de sep. de 2021 a la(s) 20:54, jbf via ntg-context (
ntg-context@ntg.nl) escribió:

> The occasional response to a similar question can be found, e.g. on
> stackexchange, but none of the responses work for me.
>
> Textadept is very fast at compiling (and does compile correctly). I can
> certainly open the pdf independently in various pdf viewers, but I
> cannot get Textadept to automatically open, say, Okular (installed on
> Linux Mint), at the end of the process.
>
> The last part of the log reads:
>
> mkiv lua stats  > runtime: 0.640 seconds, 8 processed pages, 8 shipped
> pages, 12.492 pages/second
> mtx-context | pdfview methods: auto default okular pdfxcview
> sumatra, current method: okular (directives_pdfview_method)
> pdfview | command: okular --unique "test1.pdf" 1>/dev/null
> 2>/dev/null &
> mtx-context | pdfview overhead: 0.001 seconds
> system  | total runtime: 0.649 seconds of 0.701 seconds
>
>  > exit status: 0
>
> Have tried setting up a custom text editor on okular with:
> /home/me/.textadept "%f" -e textadept.editing.goto_line(%l-1), as
> suggested by one response, but to no avail. Current version of ConTeXt
> is 2021.09.17 10:01
>
> Anyone tried Textadept successfully and might have a suggestion?
>
> Julian
>
>
> ___
> 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
>
> ___
>
___
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] Getting Textadept to open pdf?

2021-09-26 Thread jbf via ntg-context 
The occasional response to a similar question can be found, e.g. on 
stackexchange, but none of the responses work for me.


Textadept is very fast at compiling (and does compile correctly). I can 
certainly open the pdf independently in various pdf viewers, but I 
cannot get Textadept to automatically open, say, Okular (installed on 
Linux Mint), at the end of the process.


The last part of the log reads:

mkiv lua stats  > runtime: 0.640 seconds, 8 processed pages, 8 shipped 
pages, 12.492 pages/second
mtx-context | pdfview methods: auto default okular pdfxcview 
sumatra, current method: okular (directives_pdfview_method)
pdfview | command: okular --unique "test1.pdf" 1>/dev/null 
2>/dev/null &

mtx-context | pdfview overhead: 0.001 seconds
system  | total runtime: 0.649 seconds of 0.701 seconds

> exit status: 0

Have tried setting up a custom text editor on okular with: 
/home/me/.textadept "%f" -e textadept.editing.goto_line(%l-1), as 
suggested by one response, but to no avail. Current version of ConTeXt 
is 2021.09.17 10:01


Anyone tried Textadept successfully and might have a suggestion?

Julian

___
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 on style-italic vs style=italicface

2021-09-26 Thread Rik Kabel via ntg-context 

Wolfgang (off-list),

It is simply wrong to say that \italicface as defined gives only \it or 
\bi as a result. Look at the definition. If the current fontalternative 
is it \it it will give a \tf result. It is sensitive to the current 
state in a similar way that \em and \emph are, but it will always give 
an italic or roman result.


--
Rik

On 9/26/2021 18:37, Wolfgang Schuster via ntg-context wrote:

Rik Kabel via ntg-context schrieb am 27.09.2021 um 00:20:


So, I am asking whether, in places where folks often use 
style=italic, it might be better to consider style=italicface.


Bug report: \meaning\italicface gives:

protected macro:\relax \ifx \fontalternative \s!tf \it \orelse
\ifx \fontalternative
\s!bf \bi \else \tf \fi

This leaves out the transition from bi to bf. That transition is done 
by \emph, but \emph may give slanted while \italicface is always italic.




The \italicface command uses either \it or \bi as result but it never 
result in upright text and the "italic" in the name tells you this, 
there are commands (e.g. \boldface) with similar results. To get a 
slanted style you have to use the \slantedface command.


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://context.aanhet.net
archive  :https://bitbucket.org/phg/context-mirror/commits/
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Question on style-italic vs style=italicface

2021-09-26 Thread Wolfgang Schuster via ntg-context 

Rik Kabel via ntg-context schrieb am 27.09.2021 um 00:20:

On 9/26/2021 16:29, Wolfgang Schuster via ntg-context wrote:

Rik Kabel via ntg-context schrieb am 26.09.2021 um 22:13:


Hello list mavens,

What are the circumstances under which style=italicface should be 
used instead of style=italic. I note a difference when I define 
highlighting. I expected to see no difference in the line before and 
line after the hairline the example below, but see that italicface 
adapts to nesting, while italic does not:


Are there other places where this makes a difference?

\setupbodyfontenvironment
        [default]
    [em=italicface] %same with italic for this example
\definehighlight
    [emIt]
    [style=italic]
\definehighlight
    [emIf]
    [style=italicface]
\definehighlight
    [emEm]
    [style=\em]

\starttext

{\em abc {\em def} ghi}: \type{\em}

\emph{abc {\emph def} ghi}: \type{\emph}

\emEm{abc {\emEm def} ghi}: \type{\emEm \definehighlight[style=\em]}

\emIf{abc {\emIf def} ghi}: \type{\emIf
\definehighlight[style=italicface]}

\hairline

\emIt{abc {\emIt def} ghi}: \type{\emIt
\definehighlight[style=italic]}

\stoptext



The \em command has two special values which are allowed when you 
change the style with


    \setupbodyfontenvironment[default][em=...]

with the value "slanted" and "italic". When you choose one of them 
the result depends on the current weight (\tf or \bf) but with every 
other value you're just using whatever the style command/name provides.



When you pass "italicface" you're using a style which uses either \it 
or \bi dependant on the current weight. The result from the "italic" 
value doesn't depend on the behavior or the normal italic style (\it) 
which is the reason why you get different result when you use \em 
compared with \it.



Example:

\starttext

\tex{it}: normal {\it italic} {\bf bold {\it italic}}

\tex{italicface}: normal {\italicface italic} {\bf bold {\italicface 
italic}}


\tex{em}: normal {\em italic} {\bf bold {\em italic}}

\stoptext


Wolfgang 



Wolfgang,

I understand that mechanism, but I am asking a different question, I 
think.


When we specify style=\em or style=italic (and most examples I see use 
the later) in a setup of some sort, I think most folks expect similar 
behavior, but clearly it is not because italic does not track changes 
in emphasis. However, style=italicface does seem to match the behavior 
of style=\em (mostly, see the bug report below).




The basic font commands are \tf, \it, \sl, \bf, \bs and \bi and when you 
want for example bold italic text you always have to use \bi even the 
current text is already bold because \it produces normal italic text.


\em is a special case because it affects also italic text:

\starttext

\startlines
\tf normal {\em emphasized}
\sl slanted {\em emphasized}
\it italic {\em emphasized}
\bf bold {\em emphasized}
\bs bold slanted {\em emphasized}
\bi bold italic {\em emphasized}
\stoplines

\stoptext

So, I am asking whether, in places where folks often use style=italic, 
it might be better to consider style=italicface.


Bug report: \meaning\italicface gives:

protected macro:\relax \ifx \fontalternative \s!tf \it \orelse
\ifx \fontalternative
\s!bf \bi \else \tf \fi

This leaves out the transition from bi to bf. That transition is done 
by \emph, but \emph may give slanted while \italicface is always italic.




The \italicface command uses either \it or \bi as result but it never 
result in upright text and the "italic" in the name tells you this, 
there are commands (e.g. \boldface) with similar results. To get a 
slanted style you have to use the \slantedface command.


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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Question on style-italic vs style=italicface

2021-09-26 Thread Rik Kabel via ntg-context 

On 9/26/2021 16:29, Wolfgang Schuster via ntg-context wrote:

Rik Kabel via ntg-context schrieb am 26.09.2021 um 22:13:


Hello list mavens,

What are the circumstances under which style=italicface should be 
used instead of style=italic. I note a difference when I define 
highlighting. I expected to see no difference in the line before and 
line after the hairline the example below, but see that italicface 
adapts to nesting, while italic does not:


Are there other places where this makes a difference?

\setupbodyfontenvironment
        [default]
    [em=italicface] %same with italic for this example
\definehighlight
    [emIt]
    [style=italic]
\definehighlight
    [emIf]
    [style=italicface]
\definehighlight
    [emEm]
    [style=\em]

\starttext

{\em abc {\em def} ghi}: \type{\em}

\emph{abc {\emph def} ghi}: \type{\emph}

\emEm{abc {\emEm def} ghi}: \type{\emEm \definehighlight[style=\em]}

\emIf{abc {\emIf def} ghi}: \type{\emIf
\definehighlight[style=italicface]}

\hairline

\emIt{abc {\emIt def} ghi}: \type{\emIt
\definehighlight[style=italic]}

\stoptext



The \em command has two special values which are allowed when you 
change the style with


    \setupbodyfontenvironment[default][em=...]

with the value "slanted" and "italic". When you choose one of them the 
result depends on the current weight (\tf or \bf) but with every other 
value you're just using whatever the style command/name provides.



When you pass "italicface" you're using a style which uses either \it 
or \bi dependant on the current weight. The result from the "italic" 
value doesn't depend on the behavior or the normal italic style (\it) 
which is the reason why you get different result when you use \em 
compared with \it.



Example:

\starttext

\tex{it}: normal {\it italic} {\bf bold {\it italic}}

\tex{italicface}: normal {\italicface italic} {\bf bold {\italicface 
italic}}


\tex{em}: normal {\em italic} {\bf bold {\em italic}}

\stoptext


Wolfgang 



Wolfgang,

I understand that mechanism, but I am asking a different question, I think.

When we specify style=\em or style=italic (and most examples I see use 
the later) in a setup of some sort, I think most folks expect similar 
behavior, but clearly it is not because italic does not track changes in 
emphasis. However, style=italicface does seem to match the behavior of 
style=\em (mostly, see the bug report below).


So, I am asking whether, in places where folks often use style=italic, 
it might be better to consider style=italicface.


Bug report: \meaning\italicface gives:

   protected macro:\relax \ifx \fontalternative \s!tf \it \orelse \ifx
   \fontalternative
   \s!bf \bi \else \tf \fi

This leaves out the transition from bi to bf. That transition is done by 
\emph, but \emph may give slanted while \italicface is always italic.


--
Rik

___
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 on style-italic vs style=italicface

2021-09-26 Thread Wolfgang Schuster via ntg-context 

Rik Kabel via ntg-context schrieb am 26.09.2021 um 22:13:


Hello list mavens,

What are the circumstances under which style=italicface should be used 
instead of style=italic. I note a difference when I define 
highlighting. I expected to see no difference in the line before and 
line after the hairline the example below, but see that italicface 
adapts to nesting, while italic does not:


Are there other places where this makes a difference?

\setupbodyfontenvironment
        [default]
    [em=italicface] %same with italic for this example
\definehighlight
    [emIt]
    [style=italic]
\definehighlight
    [emIf]
    [style=italicface]
\definehighlight
    [emEm]
    [style=\em]

\starttext

{\em abc {\em def} ghi}: \type{\em}

\emph{abc {\emph def} ghi}: \type{\emph}

\emEm{abc {\emEm def} ghi}: \type{\emEm \definehighlight[style=\em]}

\emIf{abc {\emIf def} ghi}: \type{\emIf
\definehighlight[style=italicface]}

\hairline

\emIt{abc {\emIt def} ghi}: \type{\emIt
\definehighlight[style=italic]}

\stoptext



The \em command has two special values which are allowed when you change 
the style with


    \setupbodyfontenvironment[default][em=...]

with the value "slanted" and "italic". When you choose one of them the 
result depends on the current weight (\tf or \bf) but with every other 
value you're just using whatever the style command/name provides.



When you pass "italicface" you're using a style which uses either \it or 
\bi dependant on the current weight. The result from the "italic" value 
doesn't depend on the behavior or the normal italic style (\it) which is 
the reason why you get different result when you use \em compared with \it.



Example:

\starttext

\tex{it}: normal {\it italic} {\bf bold {\it italic}}

\tex{italicface}: normal {\italicface italic} {\bf bold {\italicface 
italic}}


\tex{em}: normal {\em italic} {\bf bold {\em italic}}

\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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Question on style-italic vs style=italicface

2021-09-26 Thread Rik Kabel via ntg-context 

Hello list mavens,

What are the circumstances under which style=italicface should be used 
instead of style=italic. I note a difference when I define highlighting. 
I expected to see no difference in the line before and line after the 
hairline the example below, but see that italicface adapts to nesting, 
while italic does not:


Are there other places where this makes a difference?

   \setupbodyfontenvironment
        [default]
    [em=italicface] %same with italic for this example
   \definehighlight
    [emIt]
    [style=italic]
   \definehighlight
    [emIf]
    [style=italicface]
   \definehighlight
    [emEm]
    [style=\em]

   \starttext

   {\em abc {\em def} ghi}: \type{\em}

   \emph{abc {\emph def} ghi}: \type{\emph}

   \emEm{abc {\emEm def} ghi}: \type{\emEm \definehighlight[style=\em]}

   \emIf{abc {\emIf def} ghi}: \type{\emIf
   \definehighlight[style=italicface]}

   \hairline

   \emIt{abc {\emIt def} ghi}: \type{\emIt \definehighlight[style=italic]}

   \stoptext

--
Rik
___
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] \placeinitial to account for quotation mark

2021-09-26 Thread Hans Hagen via ntg-context 

On 9/25/2021 10:45 PM, Thangalin via ntg-context wrote:

Henri Menke provided a partial solution:

\defineinitial[two][method={first,auto}]
\setuphead[chapter][
   after={\placeinitial[two]},
   page=no,
]

\starttext
\chapter{Harriet Tubman}
"Every great dream begins with a dreamer. Always remember, you have within
you the strength, the patience, and the passion to reach for the stars to
change the world.
\chapter{Eleanor Roosevelt}
Great minds discuss ideas; average minds discuss events; small minds
discuss people.
\stoptext

However, the leading quotation mark is gobbled. Is there any generic way 
of detecting a leading quotation mark while keeping initial caps on the 
first character?

i'll send you something off-list to test

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Framedtext : text out of frame

2021-09-26 Thread Hans Hagen via ntg-context 

On 9/26/2021 5:07 PM, Fabrice Couvreur via ntg-context wrote:

Hi,
How to fix the small problem in the code below where the text goes out 
of the frame ?

Thanks
Fabrice

\usecolors[x11]

\starttext
   \startframedtext[frame=off,width=\textwidth, 
align={broad,right},indenting={yes},background=color,backgroundcolor=navajowhite1]

       \startitemize[columns,three,n]
         \startitem
          Une quantité constante est une quantité déterminée, qui 
conserve toujours la même valeur.

         \stopitem\par
         \startitem
           Une quantité variable est une quantité indéterminée, ou, si 
l'on veut, une quantité universelle, qui comprend toutes les valeurs 
déterminées.

         \stopitem\par
         \startitem
           Une quantité variable devient déterminée, lorsqu'on lui 
attribue une valeur déterminée quelconque.

         \stopitem\par
         \startitem
           Une fonction de quantité variable est une expression 
analytique composée, de quelque manière que ce soit, de cette même 
quantité & de nombres, ou de quantités constantes.


           Par exemple, \m{a+3z} ; \m{az-4zz} ;

           \m{az+b\sqrt{aa-zz}} , cz ; \m{etc}. sont des

           fonctions de \m{z}.
         \stopitem\par
         \startitem
           Une fonction de variable est

           donc aussi une quantité variable.
         \stopitem\par
       \stopitemize
     \stopframedtext
\stoptext1
columns and framedtext etc kind of interfere here so the solution space 
becomes small


the best i can come up with now is:

\setupmixedcolumns[itemgroupcolumns][method=box,maxwidth=\availablehsize]
\startitemize[columns,three,n]
\setupalign[flushleft,broad,verytolerant,extremestretch]

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] new upload: --secure and 'dk' unit

2021-09-26 Thread Hans Hagen via ntg-context 

Hi,

I uploaded a new version. The lmtx installer should now accept --secure 
(but one has to update the installation script) in which case curl is 
used when available on the system.


There are no other chnages apart from the outrcome of an 'extension 
evening session' we had last week:


/*tex

We support the Knuthian Potrzebie cf.\ \url 
{https://en.wikipedia.org/wiki/Potrzebie} as |dk|
unit. It was added 2021-09-22 exactly when we crossed the season 
during a evening session at
the 15th \CONTEXT\ meeting in Bassenge (Boirs) Belgium. It took a 
few iterations to find the
best numerator and denominator, but Taco Hoekwater, Harald Koenig 
and Mikael Sundqvist figured
it out in this interactive session. The error messages have been 
adapted accordingly and the
scanner in the |tex| library also handle it. One |dk| is 6.43985pt. 
There is no need to make
\METAPOST\ aware of this unit because there it is just a numeric 
multiplier in a macro package.


From Wikipedia:

In issue 33, Mad published a partial table of the \quotation 
{Potrzebie System of Weights and
Measures}, developed by 19-year-old Donald E. Knuth, later a famed 
computer scientist. According
to Knuth, the basis of this new revolutionary system is the 
potrzebie, which equals the thickness

of Mad issue 26, or 2.2633484517438173216473 mm [...].

*/

This is a follow up of a suggestion by Hraban (on the meeting attendents 
list): a new unit. We have 'sp' for an unscaled unit (kind of the 
internal one, also used at the lua end), 'ex', 'em', 'px' as relative 
units (the handy ones), 'mu' for math (sort of relative and adaptive 
too), which leaves 'cm', 'mm' (popular and valid SI), 'pt' (natural to 
typesetting), 'bp' (related to postscript and pdf, the unit that 
competing-to-tex programs use), 'dd' and 'cc' (for Tomas Hala), 'in' 
(for stubborn non SI users) and now also 'dk' (for Don Knuth fans).


So, Hraban (who organizes next year meeting) can now do:

\setupbodyfont[dejavu,1dk]

\starttext

1dk = \the\dimexpr1dk = \the\dimexpr2.2633484mm

{\definedfont[Mono*none @ 6pt]test}
{\definedfont[Mono*none @ 1dk]test}

\stoptext

And in case one wonders: this few line addition doesn't harm performance.

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Framedtext : text out of frame

2021-09-26 Thread Fabrice Couvreur via ntg-context 
Hi,
How to fix the small problem in the code below where the text goes out of
the frame ?
Thanks
Fabrice

\usecolors[x11]

\starttext
  \startframedtext[frame=off,width=\textwidth,
align={broad,right},indenting={yes},background=color,backgroundcolor=navajowhite1]
  \startitemize[columns,three,n]
\startitem
 Une quantité constante est une quantité déterminée, qui conserve
toujours la même valeur.
\stopitem\par
\startitem
  Une quantité variable est une quantité indéterminée, ou, si l'on
veut, une quantité universelle, qui comprend toutes les valeurs déterminées.
\stopitem\par
\startitem
  Une quantité variable devient déterminée, lorsqu'on lui attribue
une valeur déterminée quelconque.
\stopitem\par
\startitem
  Une fonction de quantité variable est une expression analytique
composée, de quelque manière que ce soit, de cette même quantité & de
nombres, ou de quantités constantes.

  Par exemple, \m{a+3z} ; \m{az-4zz} ;

  \m{az+b\sqrt{aa-zz}} , cz ; \m{etc}. sont des

  fonctions de \m{z}.
\stopitem\par
\startitem
  Une fonction de variable est

  donc aussi une quantité variable.
\stopitem\par
  \stopitemize
\stopframedtext
\stoptext1
___
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] Regular online meet-up

2021-09-26 Thread Hans Hagen via ntg-context 

On 9/26/2021 11:03 AM, Alain Delmotte via ntg-context wrote:

Hi,

Le 25/09/2021 à 20:02, Henning Hraban Ramm via ntg-context a écrit :

Hi all,

already for a while I wanted to suggest a regular online meet-up, just to chat 
or discuss ConTeXt and the world.

Participants of the just finished meeting already know the BigBlueButton 
“room”, and without the difficulty of a auditory in presence and a weak DHCP, 
we should have even less problems with it.

I’d offer this monthly, 2–3 hours, and let’s see if it stands the test.

Now, if you’d like to participate, which times would fit you (weekdays, 
daytime...)?

Warm regards,
Hraban


What is the BigBlueButton “room”?

I am interested.

I hope that the “just finished meeting” was enjoyable, calm, not 
necessarily reposing and of course fruitful.
For sure. As were the moments between meetings, the location, and 
cuisine. It is as much a 'meeting friends' event as a 'talking tex, mp 
and lua' opportunity. A lot packed in a week. And thanks to Jano (last 
year) and Taco (this year) covid could not prevent it happening, 
although of course for some it did (which is why we experimented again 
with limited online).


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Regular online meet-up

2021-09-26 Thread Hans Hagen via ntg-context 

On 9/25/2021 8:02 PM, Henning Hraban Ramm via ntg-context wrote:

Hi all,

already for a while I wanted to suggest a regular online meet-up, just to chat 
or discuss ConTeXt and the world.

Participants of the just finished meeting already know the BigBlueButton 
“room”, and without the difficulty of a auditory in presence and a weak DHCP, 
we should have even less problems with it.

I’d offer this monthly, 2–3 hours, and let’s see if it stands the test.

Now, if you’d like to participate, which times would fit you (weekdays, 
daytime...)?
I suppose it has to be some best fit for all, so you can best check with 
those on line last week to get the best time.


Concerning 'topics' ... it if also involved discussing features, solving 
problems, demos than we need to mechanism to collect those so that they 
can be prepared.


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] \placeinitial to account for quotation mark

2021-09-26 Thread Bruce Horrocks via ntg-context 


> On 25 Sep 2021, at 21:45, Thangalin via ntg-context  
> wrote:
> 
> Henri Menke provided a partial solution:
> 
> \defineinitial[two][method={first,auto}]
> \setuphead[chapter][
>   after={\placeinitial[two]},
>   page=no,
> ]
> 
> \starttext
> \chapter{Harriet Tubman}
> "Every great dream begins with a dreamer. Always remember, you have within
> you the strength, the patience, and the passion to reach for the stars to
> change the world.
> \chapter{Eleanor Roosevelt}
> Great minds discuss ideas; average minds discuss events; small minds
> discuss people.
> \stoptext
> 
> However, the leading quotation mark is gobbled. Is there any generic way of 
> detecting a leading quotation mark while keeping initial caps on the first 
> character?
> 

Not really generic, and maybe not what you want, but there is this:

\chapter{Eleanor Roosevelt}
\setupinitial[text={"G}]
reat minds discuss ideas; average minds discuss events; small minds
discuss people.

—
Bruce Horrocks
Hampshire, UK

___
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] Regular online meet-up

2021-09-26 Thread Henning Hraban Ramm via ntg-context 

Am 2021-09-26 11:03, schrieb Alain Delmotte via ntg-context:

Hi,

What is the BigBlueButton “room”?
I am interested.


Welcome!

We’re using the facilities of the German charity “Computerwerk Darmstadt 
e.V.”; the’re very privacy-aware, their free “senfcall.de“ service is 
based on BigBlueButton (https://bigbluebutton.org).

Since I got an account, we can use the same “room” all the time:
https://lecture.senfcall.de/hen-rbr-rku-oke
I would have published the address later.


I hope that the “just finished meeting” was enjoyable, calm, not
necessarily reposing and of course fruitful.


It was, and very inspiring.
Of course, it was also too much information to process (I still can’t 
wrap my mind around MetaPost, even less LPEG).


Hraban
___
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] Regular online meet-up

2021-09-26 Thread Alain Delmotte via ntg-context 

  
  
Hi,

Le 25/09/2021 à 20:02, Henning Hraban
  Ramm via ntg-context a écrit :


  Hi all,

already for a while I wanted to suggest a regular online meet-up, just to chat or discuss ConTeXt and the world.

Participants of the just finished meeting already know the BigBlueButton “room”, and without the difficulty of a auditory in presence and a weak DHCP, we should have even less problems with it.

I’d offer this monthly, 2–3 hours, and let’s see if it stands the test.

Now, if you’d like to participate, which times would fit you (weekdays, daytime...)?

Warm regards,
Hraban

What is the BigBlueButton “room”?
I am interested.
I hope that the “just finished meeting” was enjoyable, calm, not
  necessarily reposing and of course fruitful.
Regards,
  Alain



  


___
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
___