W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2016

[Bug 30012] New: [xslt30] Syntax highlighting

From: <bugzilla@jessica.w3.org>
Date: Thu, 17 Nov 2016 16:59:22 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30012-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 30012
           Summary: [xslt30] Syntax highlighting
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Comments from Phil Fearon:

I’ve just had a quick look at your sample. I like the new style.

A couple of things I noticed which I imagine you’re already aware of,  I also
encountered these minor problems:

1. The jsp samples (jsp:setProperty) are corrupted by the XSLT rendering, they
should instead use the qf:show-xquery(.) function - which treats the jsp more
sympathetically as an XQuery element constructor. This is illustrated in the
highlight-inline.xsl changes.
2. The json snippets should also be rendered using qf:show-xquery(.) - they’re
treated as map constructors.
2. Syntax definitions containing ‘::=‘ are problematic and should probably be
skipped by the highlighter
3. The XML Schema included in H.1 line-wraps which affects formatting - you
could use XMLSpectrum’s ‘auto-trim=yes’ and ‘indent=2’ xsl parameters to
reformat this to take up less space, even if you don’t need the
syntax-highlighting here, XMLSpectrum’s formatting is described here:


You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 17 November 2016 16:59:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:03 UTC