Re: [NTG-context] Odd Font Behavior in startstop Group
On Sunday, February 6, 2022 12:58:06 AM IST Michael Urban via ntg-context
wrote:
> Do I need a newer version of ConTeXt, or am I doing something wrong?
> Fonts in ConTeXt are always perilous, alas. For me, anyway.
(pre)loading the typescripts 'fixes' the issue.
\usebodyfont[termes]
See below a modified version of your MWE:
\definefallbackfamily[story][serif][notoserif]
[range={greekandcoptic,greekextended},force=yes]
\definefontfamily[story][serif][TeX Gyre Schola]
\definefontfamily[story][sans][modern]
\definefontfamily[story][mono][modern]
\definefontfamily[story][mm][TeX Gyre Pagella Math]
\setupbodyfont[story,11pt]
\usebodyfont[termes]
\definestartstop
[blockquote]
[before={\blank\startnarrower\setupwhitespace[2pt]\setupindenting[none]},
style={\switchtobodyfont[termes]},
after={\stopnarrower\blank\indenting[next]}]
\starttext
\input knuth
\startblockquote
\input knuth
\stopblockquote
this is normal text
\par
{\bf this is bold}
\par
{\it this is italics}
\startblockquote
this is normal text
\par
{\bf this is bold}
\par
{\it this is italics}
\stopblockquote
\stoptext
Best,
Sreeram
___
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] Odd Font Behavior in startstop Group
I am experiencing an odd behavior switching text styles in a defined startstop
group ("blockquote"). I get different behavior depending on whether the
switchtobodyfont in the startstop definition includes the dummy {\it } and {\bf
} text. If they are not there, the italic and boldface switches in the second
blockquote revert to the gyreschola body font of the main text; but this only
happens if there is an earlier blockquote with no style changes. This is with:
$ context --version
mtx-context | ConTeXt Process Management 1.03
mtx-context |
mtx-context | main context file:
/usr/local/texlive/texmf-local/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2020.03.10 14:44
mtx-context | main context file:
/usr/local/texlive/texmf-local/tex/context/base/mkiv/context.mkxl
mtx-context | current version: 2020.03.10 14:44
Do I need a newer version of ConTeXt, or am I doing something wrong?
Fonts in ConTeXt are always perilous, alas. For me, anyway.
\definefallbackfamily[story][serif][notoserif][range={greekandcoptic,greekextended},force=yes]
\definefontfamily[story][serif][TeX Gyre Schola]
\definefontfamily[story][sans][modern]
\definefontfamily[story][mono][modern]
\definefontfamily[story][mm][TeX Gyre Pagella Math]
\setupbodyfont[story,11pt]
\definestartstop[blockquote]
[
before={ \blank \startnarrower \setupwhitespace[2pt] \setupindenting[none]
\switchtobodyfont[termes]{\it }{\bf }% This is so weird. Put a
comment marker after [termes] for a different result
},
after={ \stopnarrower \blank \indenting[next]},
]%
\starttext
\chapter{Testing}
\input ward
\startblockquote
\input knuth
\stopblockquote
\input zapf
{\it This is what Italic letters look like.} {\bf And these are bold.}
\startblockquote
This is what it said, in {\it Italic} and {\bf bold} letters:
\bgroup
\it\noindent This is what Italic letters look like here.
\egroup
\bgroup
\bf\noindent This is what Bold letters look like here.
\egroup
\stopblockquote
\stoptext
___
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] XMP metadata schema yields invalid PDF/A
On Sat, Feb 05, 2022 at 03:18:08PM +0100, luigi scarso wrote: > > > Following > https://www.pdfa.org/wp-content/until2016_uploads/2011/08/pdfa_metadata-2b.pdf > I think we should replace > Text > with > Lang Alt > > -- > luigi Yes, if a custom schema is needed at all (from what I can see, the XML does not embed any type definition for dc:title, for example). -- Karl Pettersson Uppsala, Sweden https://static-dust.klpn.se/ ___ 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] XMP metadata schema yields invalid PDF/A
On Sat, Feb 5, 2022 at 1:33 PM luigi scarso wrote: > > > On Sat, Feb 5, 2022 at 1:28 PM Karl Pettersson > wrote: > >> >> > >> > From what I understand, ConTeXt applies a custom Dublin Core schema >> > containing just a redefinition of dc:description, which is not coherent >> > with how dc:description is written by the application. >> > >> > This patch to lpdf-pda.xml removes the validation error. >> > >> >> Sorry, diff the other way round according to diff original new. >> > > indeed.. > Ok, now I see. Need to check some things . > -- > luigi > Following https://www.pdfa.org/wp-content/until2016_uploads/2011/08/pdfa_metadata-2b.pdf I think we should replace Text with Lang Alt -- luigi ___ 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] Regular online meet-up
You’re invited to join next Tuesday, February 8th, 15:00 CET (UTC+1) at https://lecture.senfcall.de/hen-rbr-rku-oke ConTeXt users of all levels are welcome! Hans offered to give a Q session again – please announce subjects you’d like to discuss ASAP, so that he can prepare. Regarding the date: Denis, who originally suggested Tuesday afternoon, can’t take part due to other obligations. I could also offer Wednesday or Thursday. We could also change the weekday every time, but that might be confusing. I would keep the European afternoon time, since that makes participation possible for people from America and Asia. What do you think? Vote here: https://nuudel.digitalcourage.de/tB1MHH4jx6M5uwPg (Same blurb as last time:) [Howto] * No special software installation required; most modern browsers should work (WebRTC required). * Open the above URL, accept the privacy statement, * enter your name, * click "join" (or "start" if you’re the first), * click "with microphone", allow your browser to access it, check the audio. * Your microphone is muted if you join. Activate microphone and/or camera with the buttons at the bottom. * Minimize the default presentation with the "screen" button, bottom right. * If you’d like to share your screen or upload a file, you can make yourself the presenter: Click on your user name, change the setting, then you’ll see the "screen sharing" button beside the camera button; also there’s now "manage presentations" behind the "plus" button. Beware there is only one presenter, so don’t kill someone else’s presentation. [Technical hints] * Sound is usually better if you use a headset (less noise for everyone). * Connection problems are mostly due to low bandwidth or high latency on your side, e.g. with mobile connections. * If audio/video doesn’t work for you, you can still use the text chat. * Screen sharing needs a lot of bandwidth. * You can also join with a regular telephone (audio only, of course), call +49-6151-86275-22 (German landline); then you must enter a PIN that changes every time – if you need it, ask me for it via email. Mute/unmute your microphone with "0". [Netiquette] * Please use a name that we recognize from here. Some feel uncomfortable with anonymous lurkers. * Mute your microphone while you’re not talking. * It’s nice to show your face at least when you join. * If there are connection problems, stop camera sharing. * The room is set to “everyone’s a moderator“, I trust you... See you, 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] XMP metadata schema yields invalid PDF/A
On Sat, Feb 5, 2022 at 1:28 PM Karl Pettersson wrote: > > > > > From what I understand, ConTeXt applies a custom Dublin Core schema > > containing just a redefinition of dc:description, which is not coherent > > with how dc:description is written by the application. > > > > This patch to lpdf-pda.xml removes the validation error. > > > > Sorry, diff the other way round according to diff original new. > indeed.. Ok, now I see. Need to check some things . -- luigi ___ 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] XMP metadata schema yields invalid PDF/A
> > From what I understand, ConTeXt applies a custom Dublin Core schema > containing just a redefinition of dc:description, which is not coherent > with how dc:description is written by the application. > > This patch to lpdf-pda.xml removes the validation error. > Sorry, diff the other way round according to diff original new. -- Karl Pettersson Uppsala, Sweden https://static-dust.klpn.se/ 80,97d79 < http://purl.org/dc/elements/1.1/ < pdf < Dubline Core Schema < < < < internal < Subject in Document Properties < description < Text < < < < < < < < ___ 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] XMP metadata schema yields invalid PDF/A
On Sat, Feb 05, 2022 at 09:59:44AM +0100, luigi scarso wrote: > it's not redefined -- it's dropped. And this is ok. > You can also check with > FOO > > > TITLE > > > and again it's valid. > But > https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:1:v1:en > and > https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:2:v1:en:tab:1 > suggest that dc:description and dc:title are of the same type, > which is coherent with > XMPSpecificationPart1.pdf > as in > https://github.com/adobe/XMP-Toolkit-SDK/tree/main/docs > > I.e. these are correct -- but Subject must agree with dc:description > > > > > > > > TITLE > > > > At least, this is what I understand. > >From what I understand, ConTeXt applies a custom Dublin Core schema containing just a redefinition of dc:description, which is not coherent with how dc:description is written by the application. This patch to lpdf-pda.xml removes the validation error. > -- > luigi -- Karl Pettersson, Sweden Uppsala https://static-dust.klpn.se/ 79a80,97 > > http://purl.org/dc/elements/1.1/ > pdf > Dubline Core > Schema > > > > > internal > Subject in > Document Properties > > description > > Text > > > > > > > > ___ 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] XMP metadata schema yields invalid PDF/A
On Sat, Feb 5, 2022 at 9:48 AM Karl Pettersson wrote: > > Attach metadata xml for the non-validating and validating example > (extraced with `pdfinfo -meta | xmllint format -`) in the > Github issue. > > Here is a reference to the description element. Note that only > description seems to be redefined, not title. > it's not redefined -- it's dropped. And this is ok. You can also check with FOO TITLE and again it's valid. But https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:1:v1:en and https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:2:v1:en:tab:1 suggest that dc:description and dc:title are of the same type, which is coherent with XMPSpecificationPart1.pdf as in https://github.com/adobe/XMP-Toolkit-SDK/tree/main/docs I.e. these are correct -- but Subject must agree with dc:description TITLE At least, this is what I understand. -- luigi ___ 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] XMP metadata schema yields invalid PDF/A
On Sat, Feb 05, 2022 at 12:37:44AM +0100, luigi scarso via ntg-context wrote: > On Fri, Feb 4, 2022 at 11:11 PM Karl Pettersson via ntg-context < > ntg-context@ntg.nl> wrote: > > > On Fri, Feb 04, 2022 at 10:25:27PM +0100, Hans Hagen via ntg-context wrote: > > > On 2/4/2022 7:29 PM, Karl Pettersson via ntg-context wrote: > > > > Hi > > > > > > > > PDF/A files generated using ConTeXt fail validation with veraPDF, and > > > > the reason seems to be that the dc:description metadata is defined with > > > > the wrong type in the embedded XMP extension schema. > > > > > > > > > > https://tex.stackexchange.com/questions/632380/generate-pdf-a-with-context > > > > > > > > https://github.com/veraPDF/veraPDF-library/issues/1224 > > > > > > > > I can reproduce the problem using TeX Live 2021 (MkIV 2021.03.05). The > > > > definition seems to be controlled by this code. > > > > > > > > > > https://source.contextgarden.net/tex/context/base/mkiv/lpdf-pua.xml?search=rdf#l81 > > > so "dc:description" is not permitted? it is mentioned in > > > > > > > > https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/description > > > > > > (btw it never failed before) > > > > The description element is permitted, but the problem seems to be that > > its valueType is defined as Text in the embedded schema, while the > > metadata element in the PDF has an embedded > xml:lang="x-default"> structure. > > > > > > https://github.com/veraPDF/veraPDF-library/issues/1224#issuecomment-1029932963 > > > > (I suppose the reference to "title" in the issue comment should be > > "description".) > > > > Validating with veraPDF <1.20 does not raise the error. The validation > > seems to have changed for redefined types in that version. > > > > > > https://github.com/veraPDF/veraPDF-library/blob/integration/RELEASENOTES.md#validation > > > I am missing something here... true > FOO > makes a valid pdf 3a with verapdf 1.20.1. > But dc:description is like dc:title, so where we are redefining > dc:description as Text ? > > -- > luigi Attach metadata xml for the non-validating and validating example (extraced with `pdfinfo -meta | xmllint format -`) in the Github issue. Here is a reference to the description element. Note that only description seems to be redefined, not title. https://source.contextgarden.net/tex/context/base/mkiv/lpdf-pua.xml#l81 > ___ > 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 > ___ -- Karl Pettersson Uppsala, Sweden https://static-dust.klpn.se/ http://www.w3.org/1999/02/22-rdf-syntax-ns#;> http://purl.org/dc/elements/1.1/; rdf:about=""> application/pdf AUTHOR TITLE http://ns.adobe.com/pdfx/1.3/; rdf:about=""> out | 2022-02-02T21:34:48+01:00 out 2022-02-02 21:34 www.pragma-ade.com contextgarden.net 2019.03.21 21:39 tug.org 1.10 7127 5.3 linux-64 http://ns.adobe.com/xap/1.0/; rdf:about=""> 2022-02-02T21:34:48+01:00 LuaTeX 1.10 7127 + ConTeXt MkIV 2019.03.21 21:39 2022-02-02T21:34:48+01:00 2022-02-02T21:34:48+01:00 http://ns.adobe.com/pdf/1.3/; rdf:about=""> LuaTeX-1.10 False http://ns.adobe.com/xap/1.0/mm/; rdf:about=""> uuid:77baf08a-41c6-87cb-47d0-807f764f5064 uuid:fe6c773e-42b0-864d-4c63-da5c57ec1a40 http://www.aiim.org/pdfa/ns/extension/; xmlns:pdfaProperty="http://www.aiim.org/pdfa/ns/property#; xmlns:pdfaSchema="http://www.aiim.org/pdfa/ns/schema#; rdf:about=""> http://ns.adobe.com/pdf/1.3/ pdf Adobe PDF Schema internal A name object indicating whether the document has been modified to include trapping information Trapped Text http://purl.org/dc/elements/1.1/ pdf Dubline Core Schema internal Subject in Document Properties description Text
