<?xml version="1.0" encoding="UTF-8"?>
<!-- XLIFF 2.0 replaced the 1.2 state vocabulary with exactly four ordered values — initial,
     translated, reviewed, final — and moved everything else into subState, which is namespaced
     and free-form. approved="yes|no" is gone. The mapping is therefore lossy in both directions:
     1.2 "needs-review-translation" and "needs-adaptation" both collapse to 2.0 "translated", and
     going back the other way requires a policy decision the file itself cannot record. -->
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en" trgLang="es">
  <file id="f1" original="app.strings">
    <unit id="s1">
      <segment state="initial">
        <source>Files</source>
        <target></target>
      </segment>
    </unit>
    <unit id="s2">
      <segment state="initial">
        <source>Move to trash</source>
        <target>Move to trash</target>
      </segment>
    </unit>
    <unit id="s3">
      <notes><note category="pipeline">Machine translated, awaiting human review.</note></notes>
      <segment state="translated" subState="novus:machine-translated">
        <source>Rename</source>
        <target>Renombrar</target>
      </segment>
    </unit>
    <unit id="s4">
      <segment state="translated">
        <source>Duplicate</source>
        <target>Duplicar</target>
      </segment>
    </unit>
    <unit id="s5">
      <segment state="reviewed">
        <source>Properties</source>
        <target>Propiedades</target>
      </segment>
    </unit>
    <unit id="s6" translate="no">
      <notes><note>Brand name — translate="no" means leave it alone.</note></notes>
      <segment state="final">
        <source>Novus</source>
        <target>Novus</target>
      </segment>
    </unit>
  </file>
</xliff>
