The genius of SAX starts here.
SAX的天才在这里表现了出来。
Memory isn't a problem for SAX.
内存对SAX来说不是问题。
It was a real triumph for Sax.
这是一场真正的胜利对萨克斯。
As SAX handlers go, this one is easy.
如同SAX处理器一样，这个也很简单。
有一个SAX封装器可供使用。
He would sing and I'd play my sax.
他可以唱歌，我可以吹萨克斯。
您将从SAX开始。
The main reason to adopt SAX is efficiency.
采用SAX的主要原因是效率。
Listing 4 is typical for a SAX application.
清单4是典型的SAX应用程序。
Unlike SAX, it puts your program in control.
与SAX不同，它将程序置于控制之下。
What if you do not want to use SAX at all?
如果您完全不希望使用SAX会怎样呢？
This will cause SAX to stop the parsing process.
这样将导致SAX终止解析过程。
The final type of problem in SAX is a fatal error.
SAX中问题的最后一种类型是致命错误。
The second alternative is an event API, such as SAX.
第二种选择是事件API，比如sax。
The cause of each is the same as it is with SAX.
每个问题的原因都于SAX中的一样。
Badly that it was impossible for Sax to exhibit it.
不好，这是不可能的萨克斯表现出它。
By way of background, just what is SAX? A good answer is.
考虑到背景因素，回答什么是SAX的较好答案是？
If you've never used SAX, it's easy enough to start now.
如果从没使用过SAX，那也很简单，现在就可以开始。
The traditional way to avoid these inefficiencies was to use SAX.
避免这些效率低下之处的传统方法是使用SAX。
Again, if you are familiar with SAX handlers, this class is easy.
再说一遍，如果熟悉SAX处理器，这个类就非常简单。
If you already know SAX, you're about 98 percent of the way there.
如果已经知道SAX，那么现在已经掌握大约98%的内容。
Now look at some underpinnings of SAX (complete with code examples).
现在，了解一些SAX基础知识(附有代码示例)。
This is all very typical SAX parsing; nothing here is unique to Android.
所有这些都是非常典型的SAX解析；此处的一切都不是 Android 所特有的。
Once you get this underlying instance, the usual SAX methods are available.
一旦获得该底层实例，一般的SAX方法都可用。
The first step is to get from whatever processing API that you use to SAX.
第一步是从您使用的处理API转向使用SAX。
You get the same efficiencies as with SAX, but the code is far more intuitive.
您将获得与使用 SAX 时一样的效率，但是代码将直观得多。
However, programmers must create their own object model and manage the SAX events.
然而，程序员必须创建他们自己的对象模型并管理SAX事件。
However, programmers must create their own object model and manage the SAX events.
然而，程序员必须创建他们自己的对象模型并管理SAX事件。
应用推荐