[mapserver-commits] r12683 - trunk/docs/zh_cn

[svn at osgeo.org]

Author: wbprime
Date: 2011-10-21 02:06:44 -0700 (Fri, 21 Oct 2011)
New Revision: 12683

Modified:
   trunk/docs/zh_cn/MIGRATION_GUIDE.txt
   trunk/docs/zh_cn/faq.txt
Log:
Chinese translation for q&a.txt

Modified: trunk/docs/zh_cn/MIGRATION_GUIDE.txt
===================================================================
--- trunk/docs/zh_cn/MIGRATION_GUIDE.txt	2011-10-21 08:55:47 UTC (rev 12682)
+++ trunk/docs/zh_cn/MIGRATION_GUIDE.txt	2011-10-21 09:06:44 UTC (rev 12683)
@@ -34,8 +34,7 @@
 * New (option 1)/good: TEXT ([area] + ' acres')
 * New (option 2)/good: TEXT '[area] acres'
 
-On the plus side you can now control the number of decimal places, round and even commify
-the area value for annotion.
+另外，您现在可以控制小数点的位置、小数点后的位数。
 
 详情请参见 http://mapserver.org/development/rfc/ms-rfc-64.html 和 http://trac.osgeo.org/mapserver/ticket/3736 。
 
@@ -299,19 +298,15 @@
 MapScript 的与单条查询相关的变化
 ----------------------------------------------------
 
-In RFC-52, MapServer was modified to perform queries using a single pass
-on the data instead of two passes. This is transparent for CGI applications,
-but MapScript scripts must be modified to use the layer.resultsGetShape()
-method instead of layer.getShape().
+在 RFC-52 中，MapServer 对查询的执行过程进行了改进，现在是执行单条语句而不是之前的两条。对 CGI 程序来说，这个改进不可见；但是 MapScript 的脚本必须将 layer.getShape() 方法修改为 layer.resultsGetShape()。
 
-See also: http://mapserver.org/development/rfc/ms-rfc-52.html
+参见： http://mapserver.org/development/rfc/ms-rfc-52.html
 
-(Note: the new resultsGetShape() method is not yet available for PHP MapScript 
-in 5.6.0-beta1)
+(注意：5.6.0-beta1中的新 resultsGetShape() 方法暂时还不能用于 PHP MapScript)
 
 
 ------------------------
-WFS 1.1 axis orientation
+WFS 1.1 坐标轴方向
 ------------------------
 
 The axis order in previous versions of the WFS specifications was to always use 

Modified: trunk/docs/zh_cn/faq.txt
===================================================================
--- trunk/docs/zh_cn/faq.txt	2011-10-21 08:55:47 UTC (rev 12682)
+++ trunk/docs/zh_cn/faq.txt	2011-10-21 09:06:44 UTC (rev 12683)
@@ -41,29 +41,19 @@
 MapServer是否线程安全的？
 -------------------------------------------------------------------------------
 
-**问**：MapServer是否线程安全的？
+** 问 ** ：MapServer是否线程安全的？
 
-**答**：Generally, no (but see the next question). Many components of MapServer
-use static or global data that could potentially be modified by another
-thread. Under heavy load these unlikely events become inevitable, and could
-result in sporadic errors.
+** 答 ** ：总的来说，不是（请同阅下一个问题）。 MapServer 的许多组建使用静态变量或全局变量，这些变量的值都有被其他线程修改的可能。重复加载这些组建不可避免，并且可能会导致一些错误。
 
-**Q**: Is it possible to safely use any of MapServer in a multi-threaded
-application?
+** 问 ** ：能够在多线程程序中安全地使用MapServer或者其组建吗？
 
-**A**: Some of it, yes, with care. Or with Python :) Programmers must either
-avoid using the unsafe components of MapServer or carefully place locks around
-them. Python's global interpreter lock immunizes against MapServer threading
-problems; since no mapscript code ever releases the GIL all mapscript
-functions or methods are effectively atomic. Users of mapscript and Java,
-.NET, mod_perl, or mod_php do not have this extra layer of protection.
+** 答 ** ：有一些可以很谨慎地加以使用。对于 Python 程序员来说，他们必须谨慎地选择使用 MapServer 组件，同时还得要在恰当的地方加上锁。 Python 的全局解释器锁加大 MapServer 的线程问题；由于 mapscript 代码都没有 GIL，所有的 mapscript 函数赫方法都是原子的。 mapscript 和 Java、.Net、mod_perl、或 mod_php 并没有这一层额外的安全机制。
 
-**A**: Which components are to be avoided?
+** 问 ** ：那些组件需要避免使用？
 
-**Q**: Below are lists of unsafe and unprotected components and unsafe but
-locked components.
+** 答 ** ：以下是一些不安全的组件、未受保护的组件和不安全但被锁定的组件列表：
 
-Unsafe:
+不安全的组件：
 
 - OGR layers: use unsafe CPL services 
 - Cartoline rendering: static data
@@ -74,7 +64,7 @@
 - Forcing a temporary file base (an obscure feature): static data
 - MyGIS: some static data
 
-Unsafe, but locked:
+不安全但被锁定的组件：
 
 - Map config file loading: global parser
 - Setting class and and layer filter expressions (global parser)