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
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
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:
> 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
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]
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
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
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
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
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
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.
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
> "\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":
13 matches
Mail list logo
