Hi,
there are missing \bgroup (and one \aftergroup) on line 793 and 810 in
typo-del.mkiv:
\def\typo_delimited_attributed
{\dontleavehmode
\begingroup
\dostarttaggedchained\t!delimited\currentdelimitedtext\??delimitedtext
\usedelimitedtextstyleandcolor\c!style\c!color
On Mon, Oct 23, 2017 at 11:14 PM, Peter Rolf wrote:
> Am 23.10.2017 um 19:14 schrieb Hans Hagen:
>> On 10/23/2017 7:01 PM, luigi scarso wrote:
>>> On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote:
Hans,
according to Boris Doubrov (one of
Am 23.10.2017 um 19:14 schrieb Hans Hagen:
> On 10/23/2017 7:01 PM, luigi scarso wrote:
>> On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote:
>>> Hans,
>>>
>>> according to Boris Doubrov (one of the developers of the veraPDF parser
>>> for PDF/A validation) the subtype of the
On 10/23/2017 09:53 PM, Hans Hagen wrote:
> On 10/23/2017 8:40 PM, Pablo Rodriguez wrote:
>> [...]
>> to the new content in beta 2017.10.19 13:50:
>>
>>Marked= lpdf.majorversion == 1 and pdfboolean(true) or nil,
>
> for now change that to
>
> lpdf.majorversion()
Many thanks for your
On 10/23/2017 8:40 PM, Pablo Rodriguez wrote:
Dear list,
[I accidentally discovered this issue when validating PDF/A documents
with veraPDF.]
I have the following sample:
\nopdfcompression
\setuptagging[state=start]
\starttext
\startTEXpage[offset=1em]
\TeX
Dear list,
[I accidentally discovered this issue when validating PDF/A documents
with veraPDF.]
I have the following sample:
\nopdfcompression
\setuptagging[state=start]
\starttext
\startTEXpage[offset=1em]
\TeX
\stopTEXpage
\stoptext
The resulting PDF document
On 10/23/2017 07:01 PM, luigi scarso wrote:
> [...]
> sure, but it's better if we have an example that fails
> --- I mean, the source code, the version of the parser , the command line
> used.
> It could be that other parts are also not ok.
The sample file is:
\nopdfcompression
On 10/23/2017 7:01 PM, luigi scarso wrote:
On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote:
Hans,
according to Boris Doubrov (one of the developers of the veraPDF parser
for PDF/A validation) the subtype of the /OutputIntent dictionary for
all PDF/A intents should be
On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote:
> Hans,
>
> according to Boris Doubrov (one of the developers of the veraPDF parser
> for PDF/A validation) the subtype of the /OutputIntent dictionary for
> all PDF/A intents should be GTS_PDFA1 (no GTS_PDFA2 or GTS_PDFA3).
>
Hans,
according to Boris Doubrov (one of the developers of the veraPDF parser
for PDF/A validation) the subtype of the /OutputIntent dictionary for
all PDF/A intents should be GTS_PDFA1 (no GTS_PDFA2 or GTS_PDFA3).
Here is his reply for reference:
10 matches
Mail list logo