next version

next version

[Hans Hagen via ntg-context]

Hi,

In case I forget (and someone is in wikify mode) ... the next upload 
will have a new command:

   test \diagnostic     {here 1} test
   test \diagnostic[2]  {here 2} test
   test \diagnostic[.05]{here 3} test

which will show up as

   [[diagnostic]]  > here 1
   [[diagnostic]]  > here 2 (sleep: 2)
   [[diagnostic]]  > here 3 (sleep: 0.05)

and which can be used for debugging styles. It might evolve.

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: next version

[Denis Maier via ntg-context]

> -----Ursprüngliche Nachricht-----
> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Hans Hagen
> via ntg-context
> Gesendet: Samstag, 8. Januar 2022 13:48
> An: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Cc: Hans Hagen <j.hagen@xs4all.nl>
> Betreff: [NTG-context] next version
> 
> Hi,
> 
> In case I forget (and someone is in wikify mode) ... the next upload will have
> a new command:
> 
>    test \diagnostic     {here 1} test
>    test \diagnostic[2]  {here 2} test
>    test \diagnostic[.05]{here 3} test
> 
> which will show up as
> 
>    [[diagnostic]]  > here 1
>    [[diagnostic]]  > here 2 (sleep: 2)
>    [[diagnostic]]  > here 3 (sleep: 0.05)
> 
> and which can be used for debugging styles. It might evolve.

Hans, could you give an exampe how you'd use this for debugging? I can't infer that from your example.

Denis
___________________________________________________________________________________
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
___________________________________________________________________________________

next version

[Hans Hagen]

Hi,

The next release will -apart from bug fixes and a few new things as well as the 
bib module- also miss a few things: the interface setup files, we now definitely 
move to the xml variants; as a result, texshow has been swapped for taco's 
texshow which handles the xml files directly; this is all part of a cleanup. The 
alpha relese already has these changes.

Expect also cleanup in the font area:

- csr/plr/aer/vnr will be dropped in favor of lmr (also makes minimals smaller)
- i consider run time map entries instead of file based ones
- some unused macros will be removed

btw, there is a new 'manual': tiptrick.pdf; will be extended over time

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

Re: next version

[Nikolai Weibull]

* Hans Hagen <pragma@wxs.nl> [Jan 06, 2005 17:50]:
> - csr/plr/aer/vnr will be dropped in favor of lmr (also makes minimals
> smaller)

What will this entail, exactly?
	nikolai

-- 
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

Re: next version

[Hans Hagen]

Nikolai Weibull wrote:
> * Hans Hagen <pragma@wxs.nl> [Jan 06, 2005 17:50]:
> 
>>- csr/plr/aer/vnr will be dropped in favor of lmr (also makes minimals
>>smaller)
> 
> 
> What will this entail, exactly?

less font files because latin modern has all those glyphs in it (once vietnamese 
is in there some 600 glyphs per font); for speed and consistency i may add a 
bunch of <encoding>-lmr*.tfm files but users will not notice it;

latin modern support is already present in context

another advantage is that once we default to latin modern, we have the glyoh sin 
the proper ascii slots, which means less hassle with xml

Hans



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

Re: next version

[Adam Lindsay]

Hans Hagen said this at Thu, 6 Jan 2005 18:32:27 +0100:

>>>- csr/plr/aer/vnr will be dropped in favor of lmr (also makes minimals
>>>smaller)
>> 
>> 
>> What will this entail, exactly?
>
>less font files because latin modern has all those glyphs in it (once
>vietnamese 
>is in there some 600 glyphs per font); for speed and consistency i may add a 
>bunch of <encoding>-lmr*.tfm files but users will not notice it;

Okay, here's a question: what's the plan for ec-lmr*.tfm files?

Your latin-modern typescripts accept ec, but the tfm files are called cork.
(I'm only wondering about this now for antt support.)

I know of two approaches. Which would you recommend?

\starttypescript [serif] [antykwa-torunska] [texnansi,qx,ec]
  \definefontsynonym [AntykwaTorunska-Bold]
          [\typescriptthree-anttb]     [encoding=\typescriptthree]
\stoptypescript

\starttypescript [serif] [antykwa-torunska] [ec]
  \definefontsynonym [ec-anttb] [cork-anttb]
\stoptypescript

% or...

\starttypescript [serif] [antykwa-torunska] [texnansi,qx]
  \definefontsynonym [AntykwaTorunska-Bold]
          [\typescriptthree-anttb]     [encoding=\typescriptthree]
\stoptypescript

\starttypescript [serif] [antykwa-torunska] [ec]
  \definefontsynonym [AntykwaTorunska-Bold][cork-anttb][encoding=ec]
\stoptypescript

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: next version

[h h extern]

Adam Lindsay wrote:

> Okay, here's a question: what's the plan for ec-lmr*.tfm files?

indeed a problem, i will provide an extra a typescript that maps the ec-lm* 
files onto cork-lm-*; in addition to that i will ship copies of ec-lm* as well 
as il2-lm* and pl0-lm* [or maybe polish can move to qx-lm*]; given that context 
is the only system using the encoding-name scheme, and since i have lots of ec-* 
files around, i see no reason to change ec-* to cork-*

[an option is to have something \ec that expands to ec or cork but i dislike that]

> Your latin-modern typescripts accept ec, but the tfm files are called cork.
> (I'm only wondering about this now for antt support.)

for the ant, use ec- since that's what texfont provides

> I know of two approaches. Which would you recommend?
> 
> \starttypescript [serif] [antykwa-torunska] [texnansi,qx,ec]
>   \definefontsynonym [AntykwaTorunska-Bold]
>           [\typescriptthree-anttb]     [encoding=\typescriptthree]
> \stoptypescript

easier and faster

> \starttypescript [serif] [antykwa-torunska] [ec]
>   \definefontsynonym [ec-anttb] [cork-anttb]
> \stoptypescript
> 
> % or...
> 
> \starttypescript [serif] [antykwa-torunska] [texnansi,qx]
>   \definefontsynonym [AntykwaTorunska-Bold]
>           [\typescriptthree-anttb]     [encoding=\typescriptthree]
> \stoptypescript
> 
> \starttypescript [serif] [antykwa-torunska] [ec]
>   \definefontsynonym [AntykwaTorunska-Bold][cork-anttb][encoding=ec]
> \stoptypescript

slower, the less typescripts we have ... same for lm fonts, the less the better

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

Re: next version

[Adam Lindsay]

h h extern said this at Sun, 9 Jan 2005 21:19:10 +0100:

>> Your latin-modern typescripts accept ec, but the tfm files are called cork.
>> (I'm only wondering about this now for antt support.)
>
>for the ant, use ec- since that's what texfont provides

Ah, I invoked Latin Modern because (since Jacko seems to have been behind
helping out with the release) the TeX release of Antykwa Torunska
provides the same sort of cork-* files as lm.

Anyway, I started in with some test typescripts that treat [ec/cork]
separately. (sent under separate cover)
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: next version

[Adam Lindsay]

Hans Hagen said this at Thu, 6 Jan 2005 17:44:21 +0100:

>Expect also cleanup in the font area:
>
>- csr/plr/aer/vnr will be dropped in favor of lmr (also makes minimals
>smaller)

Cool.
Not directly relevant, but if you're considering the minimals, the antt
font got a stunning update somewhere at the end of the year:
<http://www.ctan.org/tex-archive/fonts/antt/doc/fonts/antt/
AntykwaTorunska-doc-en-2_01.pdf>
<http://www.ctan.org/tex-archive/fonts/antt/>

(And I'm sure you know about Utopia being updated as well.)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: next version

[Hans van der Meer]

On Jan 6, 2005, at 17:44, Hans Hagen wrote:

>
> btw, there is a new 'manual': tiptrick.pdf; will be extended over time
>

Where can I find it? I did look for it on the pragma site but could not 
find a link to it in any of the subtrees.

May I also make a suggestion? I think it will be useful when the 
versiondate of the documents, especially the manuals, can be put along 
the download link. Like is done for the context zipped updates in the 
download page. It will make spotting updates much easier en prevents 
downloads that afterwards turn out to be duplicates. Thanks if it can 
be implemented.

Hans van der Meer

Re: next version

[Tobias Burnus]

Hi,

Hans van der Meer wrote:
> On Jan 6, 2005, at 17:44, Hans Hagen wrote:
>> btw, there is a new 'manual': tiptrick.pdf; will be extended over time
> Where can I find it? I did look for it on the pragma site but could 
> not find a link to it in any of the subtrees.
http://www.pragma-ade.com/general/manuals/tiptrick.pdf

Tobias

Re: next version

[Peter Münster]

On Fri, 7 Jan 2005, Hans van der Meer wrote:

> May I also make a suggestion? I think it will be useful when the 
> versiondate of the documents, especially the manuals, can be put along 
> the download link.

You are probably looking for this link:
http://www.pragma-ade.com/dir/general/manuals/?M=D
Cheers, Peter

-- 
http://pmrb.free.fr/contact/
_____________________________________
FilmSearch engine: http://f-s.sf.net/

Re: next version

[h h extern]

Hans van der Meer wrote:

> May I also make a suggestion? I think it will be useful when the 
> versiondate of the documents, especially the manuals, can be put along 
> the download link. Like is done for the context zipped updates in the 
> download page. It will make spotting updates much easier en prevents 
> downloads that afterwards turn out to be duplicates. Thanks if it can be 
> implemented.

maybe some day i will add some versioning to that, but currently i don't have 
that (manuals don't change that often, mostly new files are added)

you can use texsync to sync the documentation tree [uses rsync] and then you 
only update the changes [quite efficient]

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------