I describe this in the Code generation for scripting elements topic.
我在脚本元素的代码生成主题中对此进行了说明。
Several years ago, the JSP 2.0 Specification recommended that scripting elements be avoided.
多年前，JSP 2.0规范建议避免脚本元素。
It's easy to make mistakes if you choose to employ scripting elements, so they're best avoided all together.
如果选择采用脚本元素则很容易犯这样的错误，因此最好彻底避免使用脚本元素。
Once it has identified the start of one of these three scripting elements, it also has to determine where it ends.
标识了这三个脚本元素之一的开头部分后，还必须确定其结束位置。
Some scripting elements are not yet accessible though, like enumerations, but most of the functionality should be available.
尽管某些脚本元素目前并不支持，比方说enumerations，但是大部分功能对于开发者来说都是可用的。
Because the el can be used in place of JSP expressions to specify dynamic attribute values, it reduces the need for page authors to use scripting elements.
由于可以用el替代JSP表达式来指定动态属性值，因此页面创作人员无需使用脚本编制元素。
Because scripting elements can be a significant source of maintenance problems in JSP pages, providing simple (and standard) alternatives to their use is a major advantage of JSTL.
因为脚本编制元素可能是引起jsp页面中维护问题的主要原因，所以JSTL的主要优点就在于提供了这样简单(且标准)的替代方法。
Scripting elements pose a problem for XHTML compatibility.
脚本编制元素引起了XHTML兼容性问题。
Scripting elements pose a problem for XHTML compatibility.
脚本编制元素引起了XHTML兼容性问题。
应用推荐