Translate qa-bidi-source into zh-hans (#741)

xfq · web-flow · commit 33490e07728d · 2025-08-01T14:22:49.000+08:00
diff --git a/questions/qa-bidi-source-data/translations.js b/questions/qa-bidi-source-data/translations.js
@@ -1,6 +1,6 @@
 var trans = { }
 
-trans.versions = ['en']
+trans.versions = ['en', 'zh-hans']
 
 trans.outofdatetranslations = []
 
diff --git a/questions/qa-bidi-source.en.html b/questions/qa-bidi-source.en.html
@@ -1,9 +1,9 @@
 <!DOCTYPE html>
 <html lang="en">
 <head>
-<meta charset="utf-8" />
+<meta charset="utf-8">
 <title>Problems with bidirectional source text in markup</title>
-<meta name="description" content="What are some of the problems encountered when trying to write markup for bidirectional scripts?" />
+<meta name="description" content="What are some of the problems encountered when trying to write markup for bidirectional scripts?">
 <script>
 var f = { }
 
@@ -38,8 +38,8 @@
 <!--TRANSLATORS must change -en in the line just above to the subtag for their language! -->
 <script src="../javascript/doc-structure/article-2022.js"> </script>
 <script src="../javascript/articletoc-2022.js"></script>
-<link rel="stylesheet" href="../style/article-2022.css" />
-<link rel="copyright" href="#copyright"/>
+<link rel="stylesheet" href="../style/article-2022.css">
+<link rel="copyright" href="#copyright">
 <script src="../javascript/prism.js"></script>
 <link rel="stylesheet" href="../style/prism.css">
 </head>
@@ -183,7 +183,7 @@ <h2>Editing markup</h2>
 
 <section id="basedirection">
 <h2>Editing source code containing formatting characters</h2>
-<p>If you use a Unicode control character such as the <span class="uname">RIGHT TO LEFT MARK</span> (RLM) or<span class="uname"> ZERO-WIDTH NON JOINER</span> (ZWNJ), you will not usually be able to see it in the source text, since it is invisible. It is very helpful if your editor creates visible markers for these characters.</p>
+<p>If you use a Unicode control character such as the <code class="uname">RIGHT TO LEFT MARK</code> (RLM) or <code class="uname">ZERO-WIDTH NON JOINER</code> (ZWNJ), you will not usually be able to see it in the source text, since it is invisible. It is very helpful if your editor creates visible markers for these characters.</p>
 <p>You may think that a useful alternative is to use the pre-defined HTML character entities, <code>&amp;rlm;</code> and <code>&amp;zwnj;</code>, or their numeric equivalents, <code>&amp;#x200F;</code> and<code> &amp;#x200C;</code>. </p>
 <p>Unfortunately, such an approach typically has the same problems as those described in the previous section. The following example shows what you'd see if you add <code>&amp;x200F;</code> to bidirectional text in 3 different positions, in an editor that sets the context to RTL. In this simple example, the text  doesn't get moved around, but the components of the escape do.</p>
 
@@ -213,15 +213,15 @@ <h2>Editing source code containing formatting characters</h2>
 <section id="wrapping">
 <h2>Working with examples of code</h2>
 
-<p>Given the above, it will come as no surprise that creating examples for tutorials or articles can be tricky when they represent code snippets that contain RTL text. It is probably not helpful to show the text of the snippet as it would actually look in most editors; rather it would be necessary to apply extra, hidden markup to approximate something that keeps the syntax together and shows the logical order of the text. This would include markup that changes the base direction of the text where that is indicated by a <a class="kw" translate="no">dir</a> attribute value, or other method.</p>
+<p>Given the above, it will come as no surprise that creating examples for tutorials or articles can be tricky when they represent code snippets that contain RTL text. It is probably not helpful to show the text of the snippet as it would actually look in most editors; rather it would be necessary to apply extra, hidden markup to approximate something that keeps the syntax together and shows the logical order of the text. This would include markup that changes the base direction of the text where that is indicated by a <code class="kw" translate="no">dir</code> attribute value, or other method.</p>
 
 <p>Often, authors get around the issue by not showing the RTL text. For example, in all the preceding examples we removed the actual Arabic text from the main explanatory example, and just showed it in the live code examples.</p>
 
 <p>Other common ways to do this in English contexts involve representing the Arabic/Hebrew/etc. parts of the example code  by UPPERCASE TRANSLATIONS, and by using left-to-right, all-lowercase characters for the markup and any LTR text. Often, but not always, the letters in the uppercase text are written from right to left, since this allows for more realistic positioning of punctuation. Written right-to-left the uppercase text attempts to indicate the rendered result; written left-to-right, it indicates the order of characters in memory.</p>
 <p>The following provides some examples.</p>
 
 <figure id="fig_uppercase" class="example">
-<p class="browser_output_title">Uppercase translation.</p>
+<p class="browser_output_title">Uppercase translation:</p>
 <pre><code class="language-html">&lt;p class=&quot;myclass&quot; title=&quot;HEBREW&quot;&gt;INTERNATIONALIZATION ACTIVITY!&lt;/p&gt;</code></pre>
 <p class="browser_output_title">Uppercase translation with reversed direction:</p>
 <pre><code class="language-html">&lt;p class=&quot;myclass&quot; title=&quot;WERBEH&quot;&gt;!YTIVITCA NOITAZILANOITANRETNI&lt;/p&gt;</code></pre>
diff --git a/questions/qa-bidi-source.zh-hans.html b/questions/qa-bidi-source.zh-hans.html
