<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="en">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="82159e6629a3a247" weblate-flags="read-only, safe-html, strict-same">
        <source>= Frequently Asked Questions</source>
        <target state="translated">= Frequently Asked Questions</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">11</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3271495b3eebe53e" weblate-flags="read-only, safe-html, strict-same">
        <source>These libraries are not comparable. The output of</source>
        <target state="translated">These libraries are not comparable. The output of</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">13</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e8331091de11ea06" weblate-flags="read-only, safe-html, strict-same">
        <source>the simdjson parser is a read-only structure. In other words, it can't be changed, and the only way to create one is by parsing a JSON string. On the other hand, Boost.JSON allows you to modify the container holding the parsed JSON, or even build a JSON document from scratch through the container interface.</source>
        <target state="translated">the simdjson parser is a read-only structure. In other words, it can't be changed, and the only way to create one is by parsing a JSON string. On the other hand, Boost.JSON allows you to modify the container holding the parsed JSON, or even build a JSON document from scratch through the container interface.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">14</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="a8302c7bfa3f07ec" weblate-flags="read-only, safe-html, strict-same">
        <source>Using standard allocators would</source>
        <target state="translated">Using standard allocators would</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">20</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="809f39dfe82f7053" weblate-flags="read-only, safe-html, strict-same">
        <source>require that &lt;&lt;ref_value&gt;&gt; be declared as a class template, which would impose an additional compilation burden. By avoiding the template, most of the function definitions in the library can be excluded from the headers and emitted in a separate static or dynamic library.</source>
        <target state="translated">require that &lt;&lt;ref_value&gt;&gt; be declared as a class template, which would impose an additional compilation burden. By avoiding the template, most of the function definitions in the library can be excluded from the headers and emitted in a separate static or dynamic library.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">21</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="546a3103e9a0387f" weblate-flags="read-only, safe-html, strict-same">
        <source>"Why use &lt;&lt;ref_storage_ptr&gt;&gt; over {ref_polymorphic_allocator}?:: {ref_polymorphic_allocator} treats the memory resource as a reference with respect to ownership. Boost.JSON uses a reference counted smart pointer container to simplify the lifetime management of memory resources. In addition to being reference counted, &lt;&lt;ref_storage_ptr&gt;&gt; can function as an uncounted reference wrapper around a {ref_memory_resource}.</source>
        <target state="translated">"Why use &lt;&lt;ref_storage_ptr&gt;&gt; over {ref_polymorphic_allocator}?:: {ref_polymorphic_allocator} treats the memory resource as a reference with respect to ownership. Boost.JSON uses a reference counted smart pointer container to simplify the lifetime management of memory resources. In addition to being reference counted, &lt;&lt;ref_storage_ptr&gt;&gt; can function as an uncounted reference wrapper around a {ref_memory_resource}.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">26</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5bad8ad68d16c846" weblate-flags="read-only, safe-html, strict-same">
        <source>The string provided by the</source>
        <target state="translated">The string provided by the</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">34</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0e8c2e4eff21cb78" weblate-flags="read-only, safe-html, strict-same">
        <source>library uses the &lt;&lt;ref_storage_ptr&gt;&gt; allocator model, has the same interface on all C++ versions, and has an optimized class layout to keep the size of JSON values small. &lt;&lt;ref_string&gt;&gt; also implements an improved interface that replaces extraneous overloads with ones that use &lt;&lt;ref_string_view&gt;&gt;.</source>
        <target state="translated">library uses the &lt;&lt;ref_storage_ptr&gt;&gt; allocator model, has the same interface on all C++ versions, and has an optimized class layout to keep the size of JSON values small. &lt;&lt;ref_string&gt;&gt; also implements an improved interface that replaces extraneous overloads with ones that use &lt;&lt;ref_string_view&gt;&gt;.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">35</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
