1.Element, it overrides any formatter sink that might have been declared in the current channel instance or template.
元素下指定时，它重写可能已在当前信道实例或模板中声明的任何格式化程序接收器。
2.Apache FOP: Learn more about this print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter.
ApacheFOP：深入了解这个由XSL格式化对象（XSL-FO）和一个输出独立的格式化程序驱动的打印格式化程序。
3.This interface must be implemented by any class identified as a formatter in the System. Runtime. Serialization architecture.
此接口必须由任何在System.Runtime.Serialization结构中标识为格式化程序的类来实现。
4.The server formatter sink at the end of this chain will deserialize the request into a message .
此链末端的服务器格式化程序接收器将该请求反序列化为消息。
5.If you add microdata to a field formatter for your own project, you can contribute that work back to the Drupal community.
如果您在自己的项目中给字段格式器添加微数据，您可以将这些成果反馈给Drupal社区。
6.It's easy to add microdata support to a field formatter.
给字段格式器添加微数据支持十分简单。
7.Class , the formatter serializes the object into a stream and inserts it into the message body . When reading from a queue using a.
类的实例将消息发送到队列时，格式化程序将对象序列化到流中并将其插入消息体。
8.Although any number of templates can be declared , only one formatter sink can be in a channel sink call chain .
尽管可声明任意数量的模板，但在一个信道接收器调用链中只能存在一个格式化程序接收器。
9.When a message is sent to the queue, the formatter serializes an object into a stream that can be sent to the message queue.
将消息发送到队列时，格式化程序将对象序列化到可发送到消息队列的流中。
10.Each type of format can take a numerical argument as well, to tell the formatter how to properly apply the pattern.
每一种格式都会用到一个数值实参来告诉格式化程序如何适当地应用模式。