deploy: 354da49

Author: Logofile

getting-started/pythontutorial/index.html

@@ -9,7 +9,8 @@
 per-release topics, as some content is not tied to a version.</p><p>New news topics will also be published to the
 <a href=https://groups.google.com/g/protobuf>protobuf@</a> mailing list under the subject
 [Announcement].</p><h2 id=chronological>Chronological</h2><p>The following news topics provide information in the reverse order in which it
-was released.</p><ul><li><a href=/news/2025-01-23>January 23, 2025</a> - Poison Java
+was released.</p><ul><li><a href=/news/2025-03-18>March 18, 2025</a> - Dropping support
+for Ruby 3.0</li><li><a href=/news/2025-01-23>January 23, 2025</a> - Poison Java
 gencode</li><li><a href=/news/2024-12-18>December 18, 2024</a> - Go Protobuf:
 The new Opaque API</li><li><a href=/news/2024-12-13>December 13, 2024</a> - Removing
 <code>MutableRepeatedFieldRef&lt;T>::Reserve()</code> in v30</li><li><a href=/news/2024-12-04>December 4, 2024</a> - <code>DebugString</code>

news/index.html

@@ -13,11 +13,11 @@
 standard wire format for virtually everything rather than ProtoJSON format.</p><p>The encoding is described on a type-by-type basis in the table later in this
 topic.</p><p>When parsing JSON-encoded data into a protocol buffer, if a value is missing or
 if its value is <code>null</code>, it will be interpreted as the corresponding
-<a href=/programming-guides/editions#default>default value</a>. Multiple values for
-singular fields (using duplicate or equivalent JSON keys) are accepted and the
-last value is retained, as with binary format parsing. Note that not all
-protobuf JSON parser implementations are conformant, and some nonconformant
-implementations may reject duplicate keys instead.</p><p>When generating JSON-encoded output from a protocol buffer, if a protobuf field
+<a href=/programming-guides/editions#default>default value</a>.
+Multiple values for singular fields (using duplicate or equivalent JSON keys)
+are accepted and the last value is retained, as with binary format parsing. Note
+that not all protobuf JSON parser implementations are conformant, and some
+nonconformant implementations may reject duplicate keys instead.</p><p>When generating JSON-encoded output from a protocol buffer, if a protobuf field
 has the default value and if the field doesn&rsquo;t support field presence, it will
 be omitted from the output by default. An implementation may provide options to
 include fields with default values in the output.</p><p>Fields that have a value set and that support field presence always include the

programming-guides/editions/index.html

@@ -80,12 +80,12 @@
 <code>value</code>.</li><li><code>fn clear_foo(&amp;mut self)</code>: Clears the value of the field. After calling
 this, <code>has_foo()</code> will return <code>false</code> and <code>foo()</code> will return the default
 value.</li></ul><p>For other numeric field types (including <code>bool</code>), <code>int32</code> is replaced with the
-corresponding C++ type according to the
+corresponding Rust type according to the
 <a href=/programming-guides/proto3#scalar>scalar value types table</a>.</p><h3 id=implicit-presence-numeric>Implicit Presence Numeric Fields (proto3)</h3><p>For these field definitions:</p><div class=highlight><pre tabindex=0 style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-proto data-lang=proto><span style=display:flex><span><span style=color:#204a87;font-weight:700>int32</span> <span style=color:#000>foo</span> <span style=color:#ce5c00;font-weight:700>=</span> <span style=color:#0000cf;font-weight:700>1</span><span style=color:#000;font-weight:700>;</span><span style=color:#a40000>
 </span></span></span></code></pre></div><ul><li><code>fn foo(&amp;self) -> i32</code>: Returns the current value of the field. If the field
 is not set, returns <code>0</code>.</li><li><code>fn set_foo(&amp;mut self, val: i32)</code>: Sets the value of the field. After
 calling this, <code>foo()</code> will return value.</li></ul><p>For other numeric field types (including <code>bool</code>), <code>int32</code> is replaced with the
-corresponding C++ type according to the
+corresponding Rust type according to the
 <a href=/programming-guides/proto3#scalar>scalar value types table</a>.</p><h3 id=optional-string-byte>Optional String/Bytes Fields (proto2 and proto3)</h3><p>For any of these field definitions:</p><div class=highlight><pre tabindex=0 style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-proto data-lang=proto><span style=display:flex><span><span style=color:#204a87;font-weight:700>optional</span> <span style=color:#204a87;font-weight:700>string</span> <span style=color:#000>foo</span> <span style=color:#ce5c00;font-weight:700>=</span> <span style=color:#0000cf;font-weight:700>1</span><span style=color:#000;font-weight:700>;</span><span style=color:#a40000>
 </span></span></span><span style=display:flex><span><span style=color:#a40000></span><span style=color:#204a87;font-weight:700>required</span> <span style=color:#204a87;font-weight:700>string</span> <span style=color:#000>foo</span> <span style=color:#ce5c00;font-weight:700>=</span> <span style=color:#0000cf;font-weight:700>1</span><span style=color:#000;font-weight:700>;</span><span style=color:#a40000>
 </span></span></span><span style=display:flex><span><span style=color:#a40000></span><span style=color:#204a87;font-weight:700>optional</span> <span style=color:#204a87;font-weight:700>bytes</span> <span style=color:#000>foo</span> <span style=color:#ce5c00;font-weight:700>=</span> <span style=color:#0000cf;font-weight:700>1</span><span style=color:#000;font-weight:700>;</span><span style=color:#a40000>