[NTG-context] math font

2020-02-07 Thread Thomas A. Schmitz
Hi all, 

in my environment file, I have defined a math font:

\definefontfamily [thomas] [math]  [XITS Math]

and as far as I can see in the log file, this font is found:

system  >9: filename=xits-math.lfg filetype=tex 
foundname=/Users/lmtx/tex/texmf-context/tex/context/fonts/mkiv/xits-math.lfg 
fullname=/Users/lmtx/tex/texmf-context/tex/context/fonts/mkiv/xits-math.lfg 
usedmethod=database

system  >   14: filename=XITSMath-Regular.otf filetype=otf format=otf 
foundname=/Users/lmtx/tex/texmf/fonts/opentype/public/xits/XITSMath-Regular.otf 
fullname=/Users/lmtx/tex/texmf/fonts/opentype/public/xits/XITSMath-Regular.otf 
usedmethod=database

mkiv lua stats  > loaded fonts: 16 files: texgyretermes-bold.otf, 
texgyretermes-italic.otf, texgyretermes-regular.otf, xitsmath-regular.otf, 
dejavusansmono.ttf, gentiumalt-i.ttf, gentiumalt-r.ttf, myriadpro-it.otf, 
myriadpro-regular.otf, kadmosu.otf, monotype  - timesnrmtpro-bold.otf, monotype 
 - timesnrmtpro-italic.otf, monotype  - timesnrmtpro.otf, timesbold.ttf, 
timesitalic.ttf, times-roman.ttf

nevertheless, on the terminal and in the log file, I get dozens of lines with 
this message

fonts   > math: unset for global bodyfont thomas at 11pt

This is with the latest 2020.01.26 19:19. I have a slight suspicion that this 
behavior is new, but I’m not totally sure. It’s just a small nuisance, but 
something is wrong here, I would say?

All best

Thomas
___
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] math font

2020-02-07 Thread Hans Hagen

On 2/7/2020 3:34 PM, Thomas A. Schmitz wrote:




On 7. Feb 2020, at 15:14, Wolfgang Schuster  
wrote:

Does this also happen when you use \definetypeface to set the math font?

\definetypeface [thomas] [mm] [math] [xits] [default]


No, with this change, the warnings are gone. New syntax? Or user error?

I bet on user error.

We always need a math font because the math machinery has to be set up 
and context will kick in a fallback font when none has been set but that 
is done as last resort when \starttext happens. When this is done 
locally you will get the warnings. When you get a real error (abort), 
you probably have some content before fonts are set up.


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] math font

2020-02-07 Thread Wolfgang Schuster
On Fri, 7 Feb 2020 15:01:42 +0100
"Thomas A. Schmitz"  wrote:

> Hi all, 
> 
> in my environment file, I have defined a math font:
> 
> \definefontfamily [thomas] [math]  [XITS Math]
> 
> and as far as I can see in the log file, this font is found:
> 
> system  >9: filename=xits-math.lfg filetype=tex 
> foundname=/Users/lmtx/tex/texmf-context/tex/context/fonts/mkiv/xits-math.lfg 
> fullname=/Users/lmtx/tex/texmf-context/tex/context/fonts/mkiv/xits-math.lfg 
> usedmethod=database
> 
> system  >   14: filename=XITSMath-Regular.otf filetype=otf format=otf 
> foundname=/Users/lmtx/tex/texmf/fonts/opentype/public/xits/XITSMath-Regular.otf
>  
> fullname=/Users/lmtx/tex/texmf/fonts/opentype/public/xits/XITSMath-Regular.otf
>  usedmethod=database
> 
> mkiv lua stats  > loaded fonts: 16 files: texgyretermes-bold.otf, 
> texgyretermes-italic.otf, texgyretermes-regular.otf, xitsmath-regular.otf, 
> dejavusansmono.ttf, gentiumalt-i.ttf, gentiumalt-r.ttf, myriadpro-it.otf, 
> myriadpro-regular.otf, kadmosu.otf, monotype  - timesnrmtpro-bold.otf, 
> monotype  - timesnrmtpro-italic.otf, monotype  - timesnrmtpro.otf, 
> timesbold.ttf, timesitalic.ttf, times-roman.ttf
> 
> nevertheless, on the terminal and in the log file, I get dozens of lines with 
> this message
> 
> fonts   > math: unset for global bodyfont thomas at 11pt
> 
> This is with the latest 2020.01.26 19:19. I have a slight suspicion that this 
> behavior is new, but I’m not totally sure. It’s just a small nuisance, but 
> something is wrong here, I would say?

Does this also happen when you use \definetypeface to set the math font?

\definetypeface [thomas] [mm] [math] [xits] [default]

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] math font

2020-02-07 Thread Thomas A. Schmitz


> On 7. Feb 2020, at 15:14, Wolfgang Schuster 
>  wrote:
> 
> Does this also happen when you use \definetypeface to set the math font?
> 
> \definetypeface [thomas] [mm] [math] [xits] [default]

No, with this change, the warnings are gone. New syntax? Or user error?

Thomas
___
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] attachments working again (issue with /EmbeddedFiles)

2020-02-07 Thread Pablo Rodriguez
Hans,

many thanks for having fixed the issues with attachments (in latest beta
from 2020.02.07 18:36). I haven’t tested attachments with PDF/A-3a.

But there is still an issue with /EmbeddedFiles. MWE:

\setupinteraction[state=start]
\starttext
\startTEXpage[offset=1em]
a\attachment[file=abdfaeasd.txt, name=hola, method=hidden]
\contextversion
\stopTEXpage
\stoptext

File name is changed:

2 0 obj
<<
  /AFRelationship /Unspecified
  /EF <<
/F 1 0 R
  >>
  /F (hola.txt)
  /Type /Filespec
  /UF 
>>
endobj

But embedded names have the name from the file, leaving it unchanged
(abridged version):

18 0 obj
<<
  /EmbeddedFiles << /Names [ (abdfaeasd.txt) 2 0 R ] >>
  /Type /Names
>>
endobj

Could you fix the name change for /EmbeddedFiles?

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


Re: [NTG-context] Fonts from various .otf to work with \bold, \emph, \bf, \bfa ...

2020-02-07 Thread Pablo Rodriguez
On 2/7/20 8:34 AM, cont...@vivaldi.net wrote:
> Hello Pablo,
>
> thank you for showing the way; unfortunately, still something is
> missing:

Hi Lukas,

I’m afraid you missed to install the fonts in ConTeXt.

> - the resulting file uses LMRoman instead of WorkSans,

Otherwise, \definefontfamily won’t work (even if using
"tf={file:work-sans.light.otf}").

Do you have any problem installing fonts in ConTeXt? This would make
things easier.

> - Note that all WorkSans files:
> [...]
>  are placed in the same directory as the main source file. (I can zip
> them and upload somewhere for testing purposes.)

This was a feature already discussed in the past.

"\definefont[Test][file:your-font-file.otf]" should work, but I never
used this approach.

I think you need to mix fonts into a typeface with something similar to
a typescript (but this is all Greek to me).

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


Re: [NTG-context] [HOWTO] spanning xtable cells

2020-02-07 Thread Pablo Rodriguez
On 2/2/20 4:59 PM, Floris van Manen wrote:
> Can someone (please) help me out to fix the incorrect/unintended
> stacking of cells within the xtable?

Just for the record.

The issue has been fixed in latest LMTX version (from 2020.02.07 18:36).

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


Re: [NTG-context] repeat a page inside a document

2020-02-07 Thread Pablo Rodriguez
On 2/6/20 10:26 PM, Wolfgang Schuster wrote:
> On Thu, 6 Feb 2020 22:04:47 +0100 Pablo Rodriguez wrote:
>> [...]
>> At least, creating and removing empty files with Lua would be more
>> portable. And not having to use an external file would be better.
>
> Your example is still very confusing and I have no idea
> what you're trying to achieve. They way to go depends also
> what you try to achieve, when you need an exact copy of
> the first page the above is the way to go.

Sorry again for the poor explanation, Wolfgang.

I must recognize that I need this as a workaround to avoid crap at work
(and that is all I’m allowed to explain there).

I need an exact copy of the first page in the documents that only
contain a single page. Sorry, I cannot provide a minimal sample (only an
explanation [and I’m not sure it would be minimal]).

What I discovered after my previous message is that both
"\savebuffer[whatever][αβδ.γεζ]" and
"\ctxlua{os.remove([[\jobname]].."-αβδ.γεζ")}" are portable ways of
creating and removing empty files.

> Another way is to use a make file (or a ctx-file for ConTeXt)
> to add a image of the first page to your document afterwards.

I’m not sure I’m getting this: do you mean something similar to
\typesetbuffer?

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


Re: [NTG-context] attachments working again (issue with /EmbeddedFiles)

2020-02-07 Thread Rik Kabel


On 2/7/2020 14:46, Pablo Rodriguez wrote:

many thanks for having fixed the issues with attachments (in latest beta
from 2020.02.07 18:36). I haven’t tested attachments with PDF/A-3a.


PDF/A-3a attachments still fail validation with the same issues.

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


[NTG-context] suggestions for \definefontfamily and \definefallbackfamily

2020-02-07 Thread Pablo Rodriguez
Hi Wolfgang,

would it be possible that \definefontfamily could load fonts directly
(not defined in the font database), like \definefont?

\definefont[Test][file:texgyrepagella-regular.otf at 10pt]
\definefont[TestOne][file:texgyrepagella-regular-500.otf at 10pt]

\definefontfamily [mainface] [rm] [Pagella]
[tf={file:texgyrepagella-regular.otf},
 bf={file:texgyrepagella-regular-500.otf}]

\setupbodyfont[mainface]
\starttext
normal\\
\bf bold not working\\

\Test this works
\TestOne this works
\stoptext

The second improvement would be to allow "method=uppercase" with
\definefallbackfamily to be able to fake smallcaps (as used with
\definefontfallback in
https://mailman.ntg.nl/pipermail/ntg-context/2018/092878.html).

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


Re: [NTG-context] attachments working again (issue with /EmbeddedFiles)

2020-02-07 Thread Pablo Rodriguez
On 2/7/20 9:19 PM, Rik Kabel wrote:
>
> On 2/7/2020 14:46, Pablo Rodriguez wrote:
>> many thanks for having fixed the issues with attachments (in latest beta
>> from 2020.02.07 18:36). I haven’t tested attachments with PDF/A-3a.
>>
> PDF/A-3a attachments still fail validation with the same issues.

Hi Rik,

it has way less issues, at least using verapdf-1.5.18 and the following
sample:

\setuptagging[state=start]

\setupbodyfont[30pt]

\setupbackend
  [format=PDF/A-3a,
   intent=sRGB IEC61966-2.1,
   profile={sRGB.icc,default_gray.icc},
   level=0]

\setupcolors[pagecolormodel=auto]

\setupinteraction[state=start]
\starttext
\startTEXpage[offset=1em]
an attachment\attachment[file=xml-mkiv.pdf,
type={application/pdf}]
\stopTEXpage
\stoptext

With "method=hidden" (no attachment annotation) it has no issue.

Both issues are related to annotations in general:

- If the flag annotation is present (/F key), it should be set to print
and disable everything else.
- Annotations need an appearance dictionary (unless their /Rect is one
and the same point, or /Popup or /Link annotations).

Actual value of the annotation flag key is "/F null". I wonder whether
this is a bug (for having wanted to avoid the presence of /F at all).

Otherwise, I don’t think that setting all embedded file annotations to
printable is a good default.

Just in case it helps to the discussion,

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


Re: [NTG-context] attachments working again (issue with /EmbeddedFiles)

2020-02-07 Thread Hans Hagen

On 2/7/2020 9:55 PM, Pablo Rodriguez wrote:

On 2/7/20 9:19 PM, Rik Kabel wrote:


On 2/7/2020 14:46, Pablo Rodriguez wrote:

many thanks for having fixed the issues with attachments (in latest beta
from 2020.02.07 18:36). I haven’t tested attachments with PDF/A-3a.


PDF/A-3a attachments still fail validation with the same issues.


Hi Rik,

it has way less issues, at least using verapdf-1.5.18 and the following
sample:

 \setuptagging[state=start]

 \setupbodyfont[30pt]

 \setupbackend
   [format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc,default_gray.icc},
level=0]

 \setupcolors[pagecolormodel=auto]

 \setupinteraction[state=start]
 \starttext
 \startTEXpage[offset=1em]
 an attachment\attachment[file=xml-mkiv.pdf,
 type={application/pdf}]
 \stopTEXpage
 \stoptext

With "method=hidden" (no attachment annotation) it has no issue.

Both issues are related to annotations in general:

- If the flag annotation is present (/F key), it should be set to print
and disable everything else.
- Annotations need an appearance dictionary (unless their /Rect is one
and the same point, or /Popup or /Link annotations).

Actual value of the annotation flag key is "/F null". I wonder whether
this is a bug (for having wanted to avoid the presence of /F at all).

Otherwise, I don’t think that setting all embedded file annotations to
printable is a good default.

Just in case it helps to the discussion,
Peter is stepwise looking into all these issues but we decided to also 
see how that checking and standards evolve in cases where it's a 
confusing mess. And these 'appearance dicts' are an example of a mess. 
On the one hand there's predefined appearances and on the other hand 
enforced renderings which gives some chicken-egg issue. It smells a lot 
like bugs became features (standards) or 'acrobat behaviour' made the 
standard or ... (like the zero rect thing, which, given t e plenty of 
flags there are and verbosity there is in pdfm is pretty weird and 
actually can make viewers bark. Irr the current approach we follow is 
kind of a compromis.


Now, of course we can play safe and *always* have some fake appearance 
(we could basically choose whatever funny shape we like as over time 
people will interpret hard codes symbols for attachments differently) 
and drop support for standardized renderings (that could adapt over 
time).


So ... no changes etc till Peter gives his blessing as he is testing all 
this in the framework we've set up for it.


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] Fonts from various .otf to work with \bold, \emph, \bf, \bfa ...

2020-02-07 Thread Henning Hraban Ramm

> "\definefont[Test][file:your-font-file.otf]" should work, but I never
> used this approach.
> 
> I think you need to mix fonts into a typeface with something similar to
> a typescript (but this is all Greek to me).


Here’s an example of a simple typescript using "file":


\definefontfeature[smallcaps][default][smcp=yes]

\starttypescriptcollection[charis]

\starttypescript [serif] [charis]
\definefontsynonym [Charis-Roman]   [file:CharisSIL-R.ttf]
\definefontsynonym [Charis-Italic]  [file:CharisSIL-I.ttf]
\definefontsynonym [Charis-Bold][file:CharisSIL-B.ttf]
\definefontsynonym [Charis-BoldItalic]  [file:CharisSIL-BI.ttf]
\definefontsynonym [Charis-Roman-Caps]  [Charis-Roman]
\stoptypescript

\starttypescript [serif] [charis] [name]
\setups[font:fallback:serif]
\definefontsynonym [Serif][Charis-Roman][features=default]
\definefontsynonym [SerifItalic]  [Charis-Italic][features=default]
\definefontsynonym [SerifBold][Charis-Bold][features=default]
\definefontsynonym [SerifBoldItalic]  
[Charis-BoldItalic][features=default]
\definefontsynonym [SerifSlanted] [Charis-Italic][features=default]
\definefontsynonym [SerifBoldSlanted] 
[Charis-BoldItalic][features=default]
\definefontsynonym [SerifCaps]
[Charis-Roman-Caps][features=smallcaps]
\stoptypescript


\starttypescript [charis] % doesn’t make a lot of sense
  \definetypeface [charis] [rm] [serif] [charis] [default]
  \definetypeface [charis] [ss] [sans]  [heros]  [default]
  \definetypeface [charis] [tt] [mono]  [modern]   [default]
  \definetypeface [charis] [mm] [math]  [default]   [default]
\stoptypescript


\stoptypescriptcollection



Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

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