Re: [NTG-context] All NUL files in the Context distribution

2023-06-17 Thread linguafalsa--- via ntg-context 
On Sat, Jun 17, 2023 at 10:06:09AM +0200, Alain Delmotte via ntg-context wrote:
> Hi,
> 
> Le 14/06/2023 à 17:13, Leah Neukirchen via ntg-context a écrit :
> > Hi,
> > 
> > I was looking into the SciTE setup when I found that
> > tex/texmf-context/context/data/scite/context/scite-context-internal.properties
> > only contained NUL bytes.
> > 
> > Deleting and reinstalling doesn't fix it.
> > 
> > I have now checked the other files there and these files seem to have
> > gotten corrupted at some point.  Does anyone have a working copy to
> > restore them?
> > 
> > tex/texmf-context/context/data/scite/context/scite-context-internal.properties
> > tex/texmf-context/context/data/scite/context/lexers/scite-context-lexer-web-snippets.lua
> > tex/texmf-context/doc/context/sources/general/manuals/start/en/ma-cb-en-commands.tex
> > 
> > Thanks,
> 
> Same for me:
> tex/texmf-context/doc/context/sources/general/manuals/start/en/ma-cb-en-commands.tex
> contains NUL characters.
> 
> > system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.13 int:
> english/english

not only that version but also 
 ConTeXt  ver: 2023.04.27 17:04 MKIV  fmt: 2023.5.4  int: english/english

no bueno. 


> 
> --
> 
> Alain
> 
> 
> 

> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___


-- 
As long as there are ill-defined goals, bizarre bugs, and unrealistic
schedules, there will be Real Programmers willing to jump in and Solve
The Problem, saving the documentation for later.

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?

2023-06-16 Thread linguafalsa--- via ntg-context 
On Fri, Jun 16, 2023 at 06:35:49PM +0200, Gerben Wierda via ntg-context wrote:
> I know this is off topic, but I suspect this community is actually one of the 
> best places to find an answer.
> 

It is the best community. And I tell you what. 

What happened is that all TeX engines have neglected fonts from the beginning.  

> I really like Optima, and what I really like about it is the 'flared style'.
> 
> But I would like to move to a flared-sans font that gives me more licensing 
> freedom. I haven't been able to find one after extensive searching. The only 
> one who were reasonably priced (not free) were the URW Classico ones in Adobe 
> Creative Cloud, but those can only be used in Adobe programs like InDesign 
> (and not TeX).
> 

Licensing freedom is an oxymoron. There's no freedom in licensing.
Only greed. 

The only extension engine that at one point had a plan in mind,
or most of the bases covered in this regard was Omega.

When it came to commercial fonts the plan of action ahead was by
including PFC data on these very same commercial fonts that would
benefit primarily its opentype versions in the long run.

What do you have right now? Opentype fonts only. Sure. Quality can be
even the same than its type1 counterpart, and at times not so much
according so some folks that have bothered to go the extra length in
making the most accurate comparison that's available between them two.

But looking at it from a bright side/perspective, I think we're no
longer facing the same pre-historic constraints of including a font
as before, as long as it's not for commercial purposes, You are well
aware of these non and commercial uses even before  your extensive
search anyway,

p.s many many years ago I read and followed some publications about
the aformentioned extension and just went over them recently, to
have an idea what did and did not work. In regards to typefaces,
its goal was unmatched, or so I think.

> I found some flared-sans fonts, but not one with at least regular, italic, 
> bold, and bold-italic.
> 
> Is there really not a single flared-sans font that is really free (so also 
> for commercial use) to use out there?
> 
> Yours,
> 
> Gerben Wierda (LinkedIn , Mastodon 
> )
> R IT Strategy  (main site)
> Book: Chess and the Art of Enterprise Architecture 
> 
> Book: Mastering ArchiMate 
> 

> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___


-- 
I must have slipped a disk -- my pack hurts!

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Protect the lettrine

2023-06-14 Thread linguafalsa--- via ntg-context 
On Tue, Jun 13, 2023 at 08:46:59PM -0700, Thangalin via ntg-context wrote:
> Thank you for taking the time to reply, linguafalsa, I appreciate it.
> 
> The source document is written in Markdown using KeenWrite, my Markdown
> editor. Inserting typesetting instructions into the document would defeat
> the software's architecture, hence being untenable. After the Markdown is
> transformed into XHTML, a specific theme instructs ConTeXt how to typeset
> the XHTML.

Never heard of it (keenwrite), but your request is indeed, valid all along.

I haven't checked the code that lmtx uses but by just looking at the bare
macros, it seems as if `\forgetplaceinitial` is limited in what it can
and can't do. I think it's reasonable the way it was implemented but
nevertheless this is something that ought to be looked at rather than
ignore it or put aside  for later

I didn't see the video, it's distracting, but as I said, is a valid
request on your part 

Perhaps `\setuphead` can have such of a feature in the future — that
of different settings for different chapters, and if one exists now,
I'm just simply unaware of, but either way,  you're dealing mainly
here with a table and tabskips and whatnot. It seems that there's one
feature for subsubsections, written in lua, but this is entirely different

Even with something as the following I just wouldn't know how to specify
it to apply it concurrently for each particular chapter thereafter and
dissuade it from subsequently applying it to where not otherwise. I just
don't know. 


\setuphead[chapter][
  after={\placeinitial\vbox to 1cm{\relax {K{\hskip 2pt \lower 5pt \hbox{ermit 
MUffins \vbox to -0.055cm {\hskip -2.8cm \raise 1pt \hbox{meet me at the second
line}}},
  page=no, 
%]

\starttext

\startchapter[1]
\stopchapter

\forgetinitial \par

\startchapter[2]
\input knuth
\stopchapter

\stoptext


> 
> Here's a video showing how theme selection works:
> 
> https://youtu.be/3QpX70O5S30?list=PLB-WIt1cZYLm1MMx2FBG9KWzPIoWZMKu_=14
> 
> I hope this explains the situation more clearly about why changing the code
> between \starttext and \stoptext isn't an option, as you've done with
> introducing and using a macro.
> 
> Greets!

take care Tangalin 

Carlos

> 
> On Tue, Jun 13, 2023 at 7:33 PM linguafalsa--- via ntg-context <
> ntg-context@ntg.nl> wrote:
> 
> > On Tue, Jun 13, 2023 at 02:01:14PM -0700, Thangalin via ntg-context wrote:
> > > Thanks Otared,
> > >
> > > Unfortunately, that's adding content between \starttext and \stoptext,
> > > which isn't tenable in my situation. The user is writing in Markdown,
> > which
> > > is automatically converted to XHTML then passed to ConTeXt, and so the
> > > setups need to account for this scenario without modifying the source
> > > document.
> > >
> >
> > Yeah yeah yeah, tenable. A lot of things aren't tenable. Anyhow,
> > What source document are you talking about here?
> >
> > You're already sourcing the lines after chapter one. As a matter of
> > fact, if you weren't sourcing, then you'd have zilch, nada, zero, empty,
> > null, void, an space, a separation, an abstract
> >
> > Just define Kermit Muffins and it should be good to go
> >
> >
> > \setupinitial[n=2]
> >
> > \def\KermitMuffins{\vbox{Kermit Muffins\par\hskip 1.3cm \tfd Meet me at
> > the second line}}
> >
> > \setuphead[chapter][
> >   after={\placeinitial},
> >   page=no,
> > ]
> >
> > \starttext
> > \chapter{one}
> > \KermitMuffins
> >
> > \chapter{two}
> > \input knuth
> >
> > Meet me at the second line.
> > \stoptext
> >
> >
> >
> > > Cheers!
> > >
> > > On Tue, Jun 13, 2023 at 1:30 AM Otared Kavian via ntg-context <
> > > ntg-context@ntg.nl> wrote:
> > >
> > > > Hi,
> > > >
> > > > Adding \hfill\break to the short line solves the issue, but probably
> > there
> > > > is a better way to achieve the correct result.
> > > >
> > > > \setupinitial[n=2]
> > > >
> > > > \setuphead[chapter][
> > > >   after={\placeinitial},
> > > >   page=no,
> > > > ]
> > > >
> > > > \starttext
> > > > \chapter{one}
> > > > Kermit Ruffins \hfill\break % <---
> > > >
> > > > Meet me at the second line.
> > > >
> > > > \chapter{two}
> > > > \input knuth
> > > >
> > > > Meet me at the second line.
> > > > \stoptext
> > > >
> >
> >
> >
> >
> > > >
> > > >

Re: [NTG-context] Protect the lettrine

2023-06-13 Thread linguafalsa--- via ntg-context 
On Tue, Jun 13, 2023 at 02:01:14PM -0700, Thangalin via ntg-context wrote:
> Thanks Otared,
> 
> Unfortunately, that's adding content between \starttext and \stoptext,
> which isn't tenable in my situation. The user is writing in Markdown, which
> is automatically converted to XHTML then passed to ConTeXt, and so the
> setups need to account for this scenario without modifying the source
> document.
> 

Yeah yeah yeah, tenable. A lot of things aren't tenable. Anyhow,
What source document are you talking about here?

You're already sourcing the lines after chapter one. As a matter of
fact, if you weren't sourcing, then you'd have zilch, nada, zero, empty,
null, void, an space, a separation, an abstract 

Just define Kermit Muffins and it should be good to go 


\setupinitial[n=2]

\def\KermitMuffins{\vbox{Kermit Muffins\par\hskip 1.3cm \tfd Meet me at
the second line}}

\setuphead[chapter][
  after={\placeinitial},
  page=no,
]

\starttext
\chapter{one}
\KermitMuffins

\chapter{two}
\input knuth

Meet me at the second line.
\stoptext



> Cheers!
> 
> On Tue, Jun 13, 2023 at 1:30 AM Otared Kavian via ntg-context <
> ntg-context@ntg.nl> wrote:
> 
> > Hi,
> >
> > Adding \hfill\break to the short line solves the issue, but probably there
> > is a better way to achieve the correct result.
> >
> > \setupinitial[n=2]
> >
> > \setuphead[chapter][
> >   after={\placeinitial},
> >   page=no,
> > ]
> >
> > \starttext
> > \chapter{one}
> > Kermit Ruffins \hfill\break % <---
> >
> > Meet me at the second line.
> >
> > \chapter{two}
> > \input knuth
> >
> > Meet me at the second line.
> > \stoptext
> >




> >
> > Best regards: Otared
> >
> > On 13 Jun 2023, at 04:43, Thangalin via ntg-context 
> > wrote:
> >
> > I'm using KeenWrite Themes (specifically, Boschet) to typeset a chapter
> > wherein the first letter is a lettrine. When the first paragraph is too
> > short, the second paragraph overlaps the lettrine.
> >
> > % SOT
> > \setupinitial[n=2]
> >
> > \setuphead[chapter][
> >   after={\placeinitial},
> >   page=no,
> > ]
> >
> > \starttext
> > \chapter{one}
> > Kermit Ruffins
> >
> > Meet me at the second line.
> >
> > \chapter{two}
> > \input knuth
> >
> > Meet me at the second line.
> > \stoptext
> > % EOT
> >
> > Produces: https://i.stack.imgur.com/kNDqw.png
> >
> > How would you instruct ConTeXt to "protect" the lettrine such that
> > regardless of whether the first paragraph spans multiple lines, a short
> > first paragraph will still prevent the second paragraph from overlapping
> > the lettrine?
> >
> > That is, the setups should work in both cases, without any knowledge about
> > the first paragraph length being added between \starttext and \stoptext.
> >
> > ConTeXt LMTX version: 2023.06.04 18:58
> >
> > Thank you!
> >
> > ___
> > If your question is of interest to others as well, please add an entry to
> > the Wiki!
> >
> > maillist : ntg-context@ntg.nl /
> > https://www.ntg.nl/mailman/listinfo/ntg-context
> > webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> > archive  : https://bitbucket.org/phg/context-mirror/commits/
> > wiki : https://contextgarden.net
> >
> > ___
> >
> >
> > Otared Kavian
> > e-mail: ota...@gmail.com 
> > Phone: +33 6 88 26 70 95
> >
> >
> >
> >
> >
> > ___
> > If your question is of interest to others as well, please add an entry to
> > the Wiki!
> >
> > maillist : ntg-context@ntg.nl /
> > https://www.ntg.nl/mailman/listinfo/ntg-context
> > webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> > archive  : https://bitbucket.org/phg/context-mirror/commits/
> > wiki : https://contextgarden.net
> >
> > ___
> >

> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___


-- 
... an anecdote from IBM's Yorktown Heights Research Center.  When a
programmer used his new computer terminal, all was fine when he was sitting
down, but he couldn't log in to the system when he was standing up.  That
behavior was 100 percent repeatable: he could always log in when sitting and
never when standing.

Most of us just sit back and marvel at such a story; how could that terminal
know whether the poor guy was sitting or standing?  Good debuggers, though,
know that there has to be a reason.