[jboss-cvs] JBossAS SVN: r75737 - projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Jul 13 08:04:20 EDT 2008
Author: xhuang at jboss.com
Date: 2008-07-13 08:04:20 -0400 (Sun, 13 Jul 2008)
New Revision: 75737
Modified:
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po
Log:
update
Modified: projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po
===================================================================
--- projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-12 21:30:53 UTC (rev 75736)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-13 12:04:20 UTC (rev 75737)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2008-07-11 22:18+1000\n"
+"PO-Revision-Date: 2008-07-13 21:49+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
@@ -445,30 +445,31 @@
#. Tag: para
#: Configuration.xml:71
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"This is the post office that the ServerPeer uses. Normally, you wouldn't "
"have to change this attribute. The post office is responsible for routing "
"messages to queues and maintaining the mapping between addresses and queues."
-msgstr "这是 ServerPeer 使用的邮局（Post Office）。"
+msgstr ""
+"这是 ServerPeer 使用的邮局（Post Office）。通常，你不需要修改这个属性。邮局负责把消息转发至队列并维护地址和队列间的映射。"
#. Tag: title
#: Configuration.xml:76
#, no-c-format
msgid "SecurityDomain"
-msgstr ""
+msgstr "SecurityDomain"
#. Tag: para
#: Configuration.xml:77
#, no-c-format
msgid "The JAAS security domain to be used by this server peer."
-msgstr ""
+msgstr "本 server peer 使用的 JAAS 安全域名。"
#. Tag: title
#: Configuration.xml:81
#, no-c-format
msgid "DefaultSecurityConfig"
-msgstr ""
+msgstr "DefaultSecurityConfig"
#. Tag: para
#: Configuration.xml:82
@@ -478,7 +479,7 @@
"specific queue or topic has not been overridden in the destination's "
"deployment descriptor. It has exactly the same syntax and semantics as in "
"JBossMQ."
-msgstr ""
+msgstr "当特定队列或主题的安全配置没有覆盖目的地的部署描述符时，缺省的安全配置将被使用。它与在 JBossMQ 里的语法和模式完全相同。"
#. Tag: para
#: Configuration.xml:86
@@ -490,6 +491,10 @@
"literal> elements. Each <literal><role></literal> element defines the "
"default access for that particular role."
msgstr ""
+"<literal>DefaultSecurityConfig</literal> 属性元素应该包含一个 <literal>"
+"<security></literal> 元素。<literal><security></literal> 元素可以包含多个 <"
+"literal><role></literal> 元素。每个 <literal><role></literal> "
+"元素都定义了特定角色的缺省访问权限。"
#. Tag: para
#: Configuration.xml:92
@@ -499,6 +504,8 @@
"that role will be able to read (create consumers, receive messaages or "
"browse) destinations by default."
msgstr ""
+"如果 <literal>read</literal> 属性为 <literal>true</literal>"
+"，那么这个角色将缺省可以读取目的地（创建消费者、接收或浏览消息）。"
#. Tag: para
#: Configuration.xml:96
@@ -508,6 +515,8 @@
"that role will be able to write (create producers or send messages) to "
"destinations by default."
msgstr ""
+"如果 <literal>write</literal> 属性为 <literal>true</literal>"
+"，那么这个角色将缺省可以写入目的地（创建生产者或发送消息）。"
#. Tag: para
#: Configuration.xml:100
@@ -516,12 +525,14 @@
"If the <literal>create</literal> attribute is <literal>true</literal> then "
"that role will be able to create durable subscriptions on topics by default."
msgstr ""
+"如果 <literal>create</literal> 属性为 <literal>true</literal>"
+"，那么这个角色将缺省可以创建主题上的可持久订阅。"
#. Tag: title
#: Configuration.xml:105
#, no-c-format
msgid "DefaultDLQ"
-msgstr ""
+msgstr "DefaultDLQ"
#. Tag: para
#: Configuration.xml:106
@@ -537,12 +548,16 @@
"specified using the attribute DefaultMaxDeliveryAttempts for a global "
"default or individually on a per destination basis."
msgstr ""
+"这是 Server Peer 用于目的地的缺省 DLQ（Dead Letter Queue）。每个目的地的 DLQ 可以被覆盖 － 更多细节请参考目的地 "
+"MBean 的配置。DLQ 是一个特殊的目的地，当服务器递送信息连续失败指定的次数之后，这些信息将被发送到这里。如果根本就没有指定 "
+"DLQ，那么这些消息在进行最多次数的递送尝试后将被删除。递送的最多次数可以用属性 DefaultMaxDeliveryAttempts "
+"指定，它可以是全局的缺省属性也可以基于每个目的地进行设置。"
#. Tag: title
#: Configuration.xml:119
#, no-c-format
msgid "DefaultMaxDeliveryAttempts"
-msgstr ""
+msgstr "DefaultMaxDeliveryAttempts"
#. Tag: para
#: Configuration.xml:120
@@ -550,25 +565,25 @@
msgid ""
"The default for the maximum number of times delivery of a message will be "
"attempted before sending the message to the DLQ, if configured."
-msgstr ""
+msgstr "如果被设置的话，它表示消息在被发送到 DLQ 之前所尝试的最多次数。"
#. Tag: para
#: Configuration.xml:123
#, no-c-format
msgid "The default value is <literal>10</literal>."
-msgstr ""
+msgstr "它的缺省值是 <literal>10</literal>。"
#. Tag: para
#: Configuration.xml:124
#, no-c-format
msgid "This value can also be overridden on a per destination basis."
-msgstr ""
+msgstr "这个值也可以基于每个目的地进行覆盖。"
#. Tag: title
#: Configuration.xml:128
#, no-c-format
msgid "DefaultExpiryQueue"
-msgstr ""
+msgstr "DefaultExpiryQueue"
#. Tag: para
#: Configuration.xml:129
@@ -582,12 +597,15 @@
"expiry queue is not specified at all then the message will be removed after "
"it is expired."
msgstr ""
+"这是 Server Peer 用于目的地的缺省 Expiry Queue 的名称。过期时间可以基于每个目的地进行覆盖 － 更多细节请参考目的地的 "
+"MBean 配置。Expiry Queue 是一个特殊的目的地，当消息过期时将被发送到这里。消息是否过期是由 "
+"Message::getJMSExpiration() 的值决定的，如果根本没有指定 Expiry Queue，那么消息在过期后将被删除。"
#. Tag: title
#: Configuration.xml:139
#, no-c-format
msgid "DefaultRedeliveryDelay"
-msgstr ""
+msgstr "DefaultRedeliveryDelay"
#. Tag: para
#: Configuration.xml:140
@@ -596,14 +614,14 @@
"When redelivering a message after failure of previous delivery it is often "
"beneficial to introduce a delay perform redelivery in order to prevent "
"thrashing of delivery-failure, delivery-failure etc"
-msgstr ""
+msgstr "在前一次递送失败后进行重新递送前，采用一定的延迟是有益处的，这是为了阻止连续的递送失败。"
#. Tag: para
#: Configuration.xml:144
#, no-c-format
msgid ""
"The default value is <literal>0</literal> which means there will be no delay."
-msgstr ""
+msgstr "它的缺省值是 <literal>0</literal>，表示没有延迟。"
#. Tag: para
#: Configuration.xml:146
@@ -611,13 +629,13 @@
msgid ""
"Change this if your application could benefit with a delay before "
"redelivery. This value can also be overridden on a per destination basis."
-msgstr ""
+msgstr "修改这个值将使你的应用程序受益于重新递送前的延迟。这个值也可以基于每个目的地进行覆盖。"
#. Tag: title
#: Configuration.xml:151
#, no-c-format
msgid "MessageCounterSamplePeriod"
-msgstr ""
+msgstr "MessageCounterSamplePeriod"
#. Tag: para
#: Configuration.xml:152
@@ -625,19 +643,19 @@
msgid ""
"Periodically the server will query each queue to gets its statistics. This "
"is the period."
-msgstr ""
+msgstr "服务器将定期低查询每个队列来获取统计信息。这个值表示对应的时间间隔。"
#. Tag: para
#: Configuration.xml:154
#, no-c-format
msgid "The default value is <literal>10000</literal> milliseconds."
-msgstr ""
+msgstr "它的缺省值是 <literal>10000</literal> 毫秒。"
#. Tag: title
#: Configuration.xml:158
#, no-c-format
msgid "FailoverStartTimeout"
-msgstr ""
+msgstr "FailoverStartTimeout"
#. Tag: para
#: Configuration.xml:159
@@ -645,19 +663,19 @@
msgid ""
"The maximum number of milliseconds the client will wait for failover to "
"start on the server side when a problem is detected."
-msgstr ""
+msgstr "当检测到问题时，客户将等待服务器端启动失效切换的最长时间（毫秒）。"
#. Tag: para
#: Configuration.xml:162
#, no-c-format
msgid "The default value is <literal>60000</literal> (one minute)."
-msgstr ""
+msgstr "它的缺省值是 <literal>60000</literal>（亦即 1 分钟）。"
#. Tag: title
#: Configuration.xml:166
#, no-c-format
msgid "FailoverCompleteTimeout"
-msgstr ""
+msgstr "FailoverCompleteTimeout"
#. Tag: para
#: Configuration.xml:167
@@ -665,13 +683,13 @@
msgid ""
"The maximum number of milliseconds the client will wait for failover to "
"complete on the server side after it has started."
-msgstr ""
+msgstr "当失效切换已经启动时，客户将等待服务器端完成失效切换的最长时间（毫秒）。"
#. Tag: para
#: Configuration.xml:170
#, no-c-format
msgid "The default value is <literal>300000</literal> (five minutes)."
-msgstr ""
+msgstr "它的缺省值是 <literal>300000</literal>（亦即 5 分钟）。"
#. Tag: title
#: Configuration.xml:174
Modified: projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po
===================================================================
--- projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po 2008-07-12 21:30:53 UTC (rev 75736)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po 2008-07-13 12:04:20 UTC (rev 75737)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2008-07-11 14:28+1000\n"
+"PO-Revision-Date: 2008-07-13 22:03+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
@@ -290,7 +290,7 @@
#: Important_Features.xml:128
#, no-c-format
msgid "High availability and seamless fail-over"
-msgstr ""
+msgstr "高可用性和无缝式失效切换"
#. Tag: para
#: Important_Features.xml:129
@@ -301,6 +301,8 @@
"with your session seamlessly where you left off. Once and only once delivery "
"of persistent messages is respected at all times."
msgstr ""
+"如果你连接的节点出现了故障，你将自动切换至另外一个节点且不会丢失任何持久性消息。你可以从断开的地方开始无缝地继续你的会话。在任何时候，持久性消息都只会被递"
+"送一次。"
#. Tag: title
#: Important_Features.xml:134
@@ -318,12 +320,14 @@
"geographically separate clusters, forming huge globally distributed logical "
"queues and topics."
msgstr ""
+"JBoss Messaging 包含一个消息桥组件，它让你可以在处于相同或不同（如由 WAN 分隔）位置上的两个 JMS1.1 "
+"目的地之间连接消息。这允许你连接物理上独立的群集系统，从而组成大型的全球分布式逻辑队列和主题。"
#. Tag: title
#: Important_Features.xml:141
#, no-c-format
msgid "Compatibility with JBossMQ"
-msgstr ""
+msgstr "对 JBossMQ 的兼容性"
#. Tag: para
#: Important_Features.xml:142
@@ -332,6 +336,8 @@
"Since JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS code "
"written against JBossMQ will run with JBoss Messaging without any changes."
msgstr ""
+"既然 JBoss Messaging 兼容 JMS 1.1 和 JMS 1.0.2b，针对 JBossMQ 编写的 JMS 代码不作修改就可以在 "
+"JBoss Messaging 里运行。"
#. Tag: para
#: Important_Features.xml:145
@@ -341,6 +347,8 @@
"would be necessary to upgrade JBoss MQ clients with JBoss Messaging client "
"jars."
msgstr ""
+"JBoss Messaging 不具备和 JBossMQ 的线格式（wire format）兼容，JBoss MQ 客户端有必要用 JBoss "
+"Messaging 客户端的 jar 文件进行升级。"
#. Tag: para
#: Important_Features.xml:149
@@ -352,6 +360,9 @@
"Messaging. Also, the database data model is completely different, so don't "
"attempt to use JBoss Messaging with a JBoss MQ data schema and vice-versa."
msgstr ""
+"即使 JBoss Messaging 和 JBoss MQ 的部署描述符非常相似，但它们<emphasis>并不是</emphasis>"
+"相同的，所以要进行少许调整才能在 JBoss Messaging 里使用。而且，数据库数据模型完全不一样，所以请不要试图用 JBoss MQ "
+"的数据模型来使用 JBoss Messaging，反之亦然。"
#. Tag: para
#: Important_Features.xml:154
@@ -360,4 +371,6 @@
"JBoss Messaging is built against the JBoss AS 4.2 libraries which are built "
"using Java 5. Therefore JBoss Messaging only runs with Java 5 or later."
msgstr ""
+"JBoss Messaging 是采用基于 Java 5 的 JBoss AS 4.2 类库进行构建的，因此 JBoss Messaging 只能运行在 "
+"Java 5 或更新版本里。"
More information about the jboss-cvs-commits
mailing list