<?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="beddc6bb63a7c7e3" weblate-flags="read-only, safe-html, strict-same">
        <source>= Direct Conversion For large inputs parsing into the library's containers followed by conversion via &lt;&lt;ref_value_to&gt;&gt; (or vice versa &lt;&lt;ref_value_from&gt;&gt; followed by serialization from a &lt;&lt;ref_value&gt;&gt;) might be prohibitively expensive. For these cases the library provides components that allow parsing directly into and serializing directly from user-provided objects.</source>
        <target state="translated">= Direct Conversion For large inputs parsing into the library's containers followed by conversion via &lt;&lt;ref_value_to&gt;&gt; (or vice versa &lt;&lt;ref_value_from&gt;&gt; followed by serialization from a &lt;&lt;ref_value&gt;&gt;) might be prohibitively expensive. For these cases the library provides components that allow parsing directly into and serializing directly from user-provided objects.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">10</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="975563e8e146aef3" weblate-flags="read-only, safe-html, strict-same">
        <source>The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are. Also all objects that should be populated by parsing have to be default constructible types. This includes not only the top-level object, but e.g. elements of containers, members of described `struct`s, and alternatives of variants.</source>
        <target state="translated">The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are. Also all objects that should be populated by parsing have to be default constructible types. This includes not only the top-level object, but e.g. elements of containers, members of described `struct`s, and alternatives of variants.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">17</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="df1a22029ed95a47" weblate-flags="read-only, safe-html, strict-same">
        <source>That being said, if your types are default-constructible and you don't need the customisability allowed by &lt;&lt;ref_value_to&gt;&gt; and &lt;&lt;ref_value_from&gt;&gt;, then you can get a significant performance boost with direct conversions.</source>
        <target state="translated">That being said, if your types are default-constructible and you don't need the customisability allowed by &lt;&lt;ref_value_to&gt;&gt; and &lt;&lt;ref_value_from&gt;&gt;, then you can get a significant performance boost with direct conversions.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">23</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2582914d2a07ba9f" weblate-flags="read-only, safe-html, strict-same">
        <source>Direct parsing is performed by the &lt;&lt;ref_parse_into&gt;&gt; family of functions. The library provides overloads that take either &lt;&lt;ref_string_view&gt;&gt; or `std::istream`, and can report errors either via throwing exceptions or setting an error code.</source>
        <target state="translated">Direct parsing is performed by the &lt;&lt;ref_parse_into&gt;&gt; family of functions. The library provides overloads that take either &lt;&lt;ref_string_view&gt;&gt; or `std::istream`, and can report errors either via throwing exceptions or setting an error code.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">27</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8e87e2f3741a4750" weblate-flags="read-only, safe-html, strict-same">
        <source>If you need to combine incremental parsing with direct parsing, you can resort to &lt;&lt;ref_parser_for&gt;&gt;. `parser_for&lt;T&gt;` is an instantiation of &lt;&lt;ref_basic_parser&gt;&gt; that parses into an object of type `T`, and is what &lt;&lt;ref_parse_into&gt;&gt; uses under the hood.</source>
        <target state="translated">If you need to combine incremental parsing with direct parsing, you can resort to &lt;&lt;ref_parser_for&gt;&gt;. `parser_for&lt;T&gt;` is an instantiation of &lt;&lt;ref_basic_parser&gt;&gt; that parses into an object of type `T`, and is what &lt;&lt;ref_parse_into&gt;&gt; uses under the hood.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">37</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="63941b33aef11bc0" weblate-flags="read-only, safe-html, strict-same">
        <source>Direct serialization doesn't require any special components and works with the regular &lt;&lt;ref_serializer&gt;&gt; and &lt;&lt;ref_serialize&gt;&gt;.</source>
        <target state="translated">Direct serialization doesn't require any special components and works with the regular &lt;&lt;ref_serializer&gt;&gt; and &lt;&lt;ref_serialize&gt;&gt;.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile"></context>
          <context context-type="linenumber">42</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
