@qt4cg statuses in 2026

This page displays status updates about the QT4 CG project from 2026.

See also recent statuses.

QT4 CG meeting 147 draft minutes #minutes-01-06

06 Jan at 17:15:00 GMT
Link: https://qt4cg.org/meeting/minutes/2026/01-06

Draft minutes published.

Issue #407 closed #closed-407

06 Jan at 16:58:54 GMT
Link: https://github.com/qt4cg/qtspecs/issues/407

XSLT-specific context properties used in function items

Issue #2274 closed #closed-2274

06 Jan at 16:58:53 GMT
Link: https://github.com/qt4cg/qtspecs/pull/2274

407 Function items capturing XSLT context components

Issue #1011 closed #closed-1011

06 Jan at 16:55:55 GMT
Link: https://github.com/qt4cg/qtspecs/issues/1011

fn:transform() improvements

Issue #2348 closed #closed-2348

06 Jan at 16:55:54 GMT
Link: https://github.com/qt4cg/qtspecs/pull/2348

1011 fn transform improvements

Issue #2339 closed #closed-2339

06 Jan at 16:52:33 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2339

Default priority of match="element(A|B)"

Issue #2335 closed #closed-2335

06 Jan at 16:52:32 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2335

Make `jnode()` like `element()`

Issue #2334 closed #closed-2334

06 Jan at 16:52:32 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2334

XSLT: Parenthesized subexpressions within Patterns

Issue #2297 closed #closed-2297

06 Jan at 16:52:32 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2297

XSLT pattern ambiguities with typed matches

Issue #2336 closed #closed-2336

06 Jan at 16:52:31 GMT
Link: https://github.com/qt4cg/qtspecs/pull/2336

2334 Revise XSLT pattern syntax and semantics

Issue #2048 closed #closed-2048

06 Jan at 16:51:41 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2048

Untrusted execution, and security more generally

Pull request #2358 created #created-2358

05 Jan at 16:26:16 GMT
Link: https://github.com/qt4cg/qtspecs/pull/2358
2357 Standardize on element() rather than element(*)

Fix #2357

Issue #2357 created #created-2357

05 Jan at 16:12:28 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2357
element() vs element(*) in function signatures

We use element(*) and element() interchangeably in function signatures. I propose we standardise on the simpler form, element().

Ditto attribute().

Issue #2356 created #created-2356

05 Jan at 15:34:47 GMT
Link: https://github.com/qt4cg/qtspecs/issues/2356
Clarification on scope of variables in xsl:for-each-group/(@split-when|@merge-when)

A user experimenting with xsl:for-each-group/@split-when with my 4->3 source-code transformer, inferred that the variable $group was available within the sequence constructor of the grouping instruction.

(Unfortunately due to an error in my transformer code $group was within scope in the sequence constructor, though with the wrong value ;-) - this has since been corrected.)

A close and detailed reading of the spec shows that $group and $next are implied as only in scope for the evaluation of the @split-when expression. Might I suggest that there is a small note emphasising this is the case? Similar clarification may be worthwhile for @merge-when too.

QT4 CG meeting 147 draft agenda #agenda-01-06

05 Jan at 12:00:00 GMT
Link: https://qt4cg.org/meeting/agenda/2026/01-06

Draft agenda published.