File: parser-xslt.rst

package info (click to toggle)
codelite 17.0.0%2Bdfsg-6
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 136,384 kB
  • sloc: cpp: 491,550; ansic: 280,393; php: 10,259; sh: 8,930; lisp: 7,664; vhdl: 6,518; python: 6,020; lex: 4,920; yacc: 3,123; perl: 2,385; javascript: 1,715; cs: 1,193; xml: 1,110; makefile: 805; cobol: 741; sql: 709; ruby: 620; f90: 566; ada: 534; asm: 464; fortran: 350; objc: 289; tcl: 258; java: 157; erlang: 61; pascal: 51; ml: 49; awk: 44; haskell: 36
file content (22 lines) | stat: -rw-r--r-- 923 bytes parent folder | download | duplicates (8) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
.. _xslt:

======================================================================
XSLT parser
======================================================================

:Maintainer: Masatake YAMATO <yamato@redhat.com>

This parser only supports XSLT 1.0.
If a newer version (2.0 and 3.0) is specified in an input file, ctags
just skips the input. With ``--verbose``, ctags prints the detected
version of the input file.

Scope information generated by the XSLT parser is a bit broken.
Currently a period (`.`) is used as the separator in nested scopes.
This is the default separator value in ctags.

When the XSLT parser captures a node `<xsl:template match="...">` the
value of the `match` attribute is tagged with kind `matchedTemplate`.
When a `matchedTemplate` name is stored as part of the scope information,
client tools may be confused because `.` is used both as the scope separator
and in the XPath match expression.