<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Dear Stephanie and Galen,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Thank you very much for bringing up the
      issue!</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Galen, your insight that POEditor is
      not actually involved, although these string are used in the staff
      client, is indeed a valuable one!</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">The examples in rows 8 to 12 in the
      file
<a class="moz-txt-link-freetext" href="https://docs.google.com/spreadsheets/d/13_AwTRNLobGIgA6bFqw0pC3tWXq8D8i13CshCbOb1u4/edit?usp=sharing">https://docs.google.com/spreadsheets/d/13_AwTRNLobGIgA6bFqw0pC3tWXq8D8i13CshCbOb1u4/edit?usp=sharing</a>
      might indicate that we have the translations available but they
      are just not getting properly displayed in the interface.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">In our installations we use both
      English and Czech, so I suppose the replacement for the
      single-language site wouldn't be the right option for us as these
      would actually count as two languages rather than one (?). <br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Linda</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 2/22/24 00:29, Galen Charlton via
      Evergreen-dev wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPLnt65D2kHgDTe6f7SWaUkhvgsXTQr+ufF0Vf6c=MRAfMg+MA@mail.gmail.com">
      <div dir="ltr">
        <div>Hi,</div>
        <div><br>
        </div>
        <div>Upon checking, POEditor is not involved. Labels from the
          IDL are translated via Launchpad - for example, <a
href="https://translations.launchpad.net/evergreen/main/+pots/fm-idl.dtd/cs/+translate"
            moz-do-not-send="true" class="moz-txt-link-freetext">https://translations.launchpad.net/evergreen/main/+pots/fm-idl.dtd/cs/+translate</a>.</div>
        <div><br>
        </div>
        <div>The way that the mechanism is supposed to work is that a
          version of fm_IDL.xml is produced that uses XML entities. In
          the tarball, that version gets produced as
          Open-ILS/web/reports/fm_IDL.xml. The translations are written
          to DTD files, e.g.,
          ./Open-ILS/web/opac/locale/cs-CZ/fm_IDL.dtd in the tarball.</div>
        <div><br>
        </div>
        <div>The entity version of fm_IDL.xml goes in
          /openils/var/reports; the DTD files for each desired local
          goes in /openils/var/web/opac/locale/$LOCALE, e.g.,
          /openils/var/web/opac/locale/cs-CZ/fm_IDL.dtd.</div>
        <div><br>
        </div>
        <div>The entity version of fm_IDL.xml includes the following
          line to select the right DTD to load the translation
          dynamically:</div>
        <div><br>
        </div>
        <div>     <!--#include
          virtual="/opac/locale/${locale}/fm_IDL.dtd"--> </div>
        <div><br>
        </div>
        <div>For a single-language site, "${locale}" could be replaced
          with a single locale value.</div>
        <div><br>
        </div>
        <div>As far as I can tell, the I18N instructions during the
          release process are doing the right thing; what's missing is
          effective documentation or installation tools to automatically
          install the right stuff. What we have at the moment is this
          email, this [1], and some content on the wiki that doesn't
          discuss the IDL translation in particular, as far as I can
          tell.</div>
        <div><br>
        </div>
        <div>So, the components are present, just, to put it politely,
          underdocumented.<br>
        </div>
        <div><br>
        </div>
        <div>[1] <a
href="https://docs.evergreen-ils.org/docs/latest/reports/reporter_add_data_source.html#_add_a_new_class_to_fm_idl_xml_for_your_data_source"
            moz-do-not-send="true" class="moz-txt-link-freetext">https://docs.evergreen-ils.org/docs/latest/reports/reporter_add_data_source.html#_add_a_new_class_to_fm_idl_xml_for_your_data_source</a></div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div><br>
        </div>
        <div>Galen<br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Wed, Feb 21, 2024 at
          5:24 PM Stephanie Leary via Evergreen-dev <<a
            href="mailto:evergreen-dev@list.evergreen-ils.org"
            moz-do-not-send="true" class="moz-txt-link-freetext">evergreen-dev@list.evergreen-ils.org</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote">
          <div dir="ltr">
            <div>Hi, all. I want to revisit the issue of missing
              translations that Linda brought up on Jan. 2. If I
              understand correctly, the main problem is that we have
              strings in the IDL that are not being imported into
              POEditor.<br>
            </div>
            <div><br>
            </div>
            <div>This is the procedure the 3.12 release team used:</div>
            <div><a
href="https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:how_to_build"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:how_to_build</a></div>
            <div><br>
            </div>
            <div>As you can see, there are several steps related to
              translations.</div>
            <div><br>
            </div>
            <div>The POEditor instructions are here:<br>
            </div>
            <div><a
href="https://wiki.evergreen-ils.org/doku.php?id=poeditor"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://wiki.evergreen-ils.org/doku.php?id=poeditor</a></div>
            <div><br>
            </div>
            <div>Are we missing some steps?<br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>
              <div dir="ltr" class="gmail_signature">
                <div dir="ltr">Stephanie Leary<br>
                  Front End Developer<br>
                  Equinox Open Library Initiative<br>
                  <a class="moz-txt-link-abbreviated" href="mailto:stephanie.leary@equinoxOLI.org">stephanie.leary@equinoxOLI.org</a><br>
                  <a href="https://www.equinoxOLI.org" target="_blank"
                    moz-do-not-send="true">https://www.equinoxOLI.org</a><br>
                  phone: 877-OPEN-ILS (673-6457)</div>
              </div>
            </div>
            <br>
          </div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Tue, Jan 2, 2024 at
              12:23 AM Linda Jansová via Evergreen-general <<a
                href="mailto:evergreen-general@list.evergreen-ils.org"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">evergreen-general@list.evergreen-ils.org</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote">Dear all,<br>
              <br>
              We have begun working with the 3.12 version which is -
              when it comes to <br>
              correctly displaying Czech - significantly better than the
              previous <br>
              version - of course a big thank you goes out to everyone
              who has helped <br>
              along the way :-)!<br>
              <br>
              One of the so far unresolved issues we would like to start
              working on <br>
              now are the column headers. These often remain
              untranslated as we have <br>
              reported here:<br>
              <br>
              <a
                href="https://bugs.launchpad.net/evergreen/+bug/2042915"
                rel="noreferrer" target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://bugs.launchpad.net/evergreen/+bug/2042915</a><br>
              <br>
              There is also a spreadsheet with a couple of examples:<br>
              <br>
              <a
href="https://docs.google.com/spreadsheets/d/13_AwTRNLobGIgA6bFqw0pC3tWXq8D8i13CshCbOb1u4/edit?usp=sharing"
                rel="noreferrer" target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://docs.google.com/spreadsheets/d/13_AwTRNLobGIgA6bFqw0pC3tWXq8D8i13CshCbOb1u4/edit?usp=sharing</a><br>
              <br>
              It seems that if the string (and, consequently, its
              translation) is not <br>
              present in POEditor and can only be found on Launchpad and
              in fm_IDL.xml <br>
              and in translation files in GIT, the staff client
              interface shows the <br>
              English string instead of the Czech one.<br>
              <br>
              So I was just wondering how we could proceed, e.g. should
              we try to <br>
              compile a comprehensive list of all missing translations
              from the column <br>
              headers? And if so, which other pieces of information
              would be useful to <br>
              add, e.g., would a spreadsheet like the one mentioned
              above be a good <br>
              starting point?<br>
              <br>
              In some cases when the string is not very unique
              (actually, it is a <br>
              rather common situation to come across widely used
              strings; the unique <br>
              ones appear less frequently), the GIT links might not be
              very useful as <br>
              the string would be found in many more places (and,
              consequently, files) <br>
              than just say in a single column header.<br>
              <br>
              Perhaps trying to locate relevant ".component.html" files
              with missing <br>
              i18n-label attributes (using <br>
              <a
href="https://git.evergreen-ils.org/?p=Evergreen.git&a=search&h=HEAD&st=grep&s=+%3Ceg-grid-column"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://git.evergreen-ils.org/?p=Evergreen.git&a=search&h=HEAD&st=grep&s=+%3Ceg-grid-column</a>
              <br>
              or a similar approach) would be a better choice? (But
              maybe this <br>
              wouldn't work in practice as the example strings from the
              spreadsheet <br>
              currently indicate no occurrences in the .component.html
              files.)<br>
              <br>
              Or would there be an entirely different way to tackle it?<br>
              <br>
              Thank you very much for sharing your views!<br>
              <br>
              Linda<br>
              <br>
              _______________________________________________<br>
              Evergreen-general mailing list<br>
              <a href="mailto:Evergreen-general@list.evergreen-ils.org"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">Evergreen-general@list.evergreen-ils.org</a><br>
              <a
href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general"
                rel="noreferrer" target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
            </blockquote>
          </div>
          _______________________________________________<br>
          Evergreen-dev mailing list<br>
          <a href="mailto:Evergreen-dev@list.evergreen-ils.org"
            target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">Evergreen-dev@list.evergreen-ils.org</a><br>
          <a
href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev"
            rel="noreferrer" target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <span class="gmail_signature_prefix">-- </span><br>
      <div dir="ltr" class="gmail_signature">
        <div dir="ltr">Galen Charlton<br>
          Implementation and IT Manager<br>
          Equinox Open Library Initiative<br>
          <a href="mailto:gmc@equinoxOLI.org" target="_blank"
            moz-do-not-send="true" class="moz-txt-link-freetext">gmc@equinoxOLI.org</a><br>
          <a href="https://www.equinoxOLI.org" target="_blank"
            moz-do-not-send="true">https://www.equinoxOLI.org</a> <br>
          phone: 877-OPEN-ILS (673-6457)<br>
          direct: 770-709-5581<br>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Evergreen-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-dev@list.evergreen-ils.org">Evergreen-dev@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>