Yes, we could say that in the spec. We could also limit the "shorthand" to direct children of cs:substitute.
Rintze > I'd say that in the case of placing cs:names inside cs:substitute, style > authors must be aware of the inheritance rules; therefore, if they do > not want to inherit the cs:name node from above, they would put an empty > cs:name node inside the nested cs:names to make this clear, don't you > think? > >> Perhaps we should consider >> limiting cs:substitute in future versions of CSL, and e.g. only allow >> the cs:names shorthand and cs:text (to call variables and macros) as >> children. Anything complex can then be moved out into a macro. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
