<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>a) everything you have described involves characters, not glyphs.</p>
    <p>b) machine translation already works at the receiving end, and is
      able to handle arbitrary text (and speech) rather than being
      limited to a set of string localisations.</p>
    <p>JH<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2024-10-01 12:41, William_J_G
      Overington via mpeg-otspec wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:3ee7afcc.2503a.192499a0774.Webtop.250@btinternet.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <p><span style="font-family:Arial, sans-serif;font-size:18px;">John
          Hudson replied.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Thank
          you for replying.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">John
          Hudson wrote as follows.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">>
          You are proposing breaking something that already works in
          order to make it work in a more convoluted and less useful
          way.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">I am
          not proposing breaking anything, I am suggesting an additional
          facility.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">I do
          not purport to know much about localization. So maybe I have
          got it wrong.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So I
          will try to explain my thinking and readers can decide whether
          this is a new idea, and if so, what they opine about it and
          about my suggested new layout feature becoming added to the
          font standard.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Around
          2009 there was lots of discussion about whether to encode
          emoji each as a character in ISO/IEC 10646.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">I
          wondered what else could be encoded as a character.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Letters,
          digits, punctuation, spaces, symbols - some of each of those
          had been encoded.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">"What
          about whole sentences?" I thought.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So I
          did a thought experiment.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Consider
          a sentence such as "It is snowing.".</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Suppose
          that that sentence is encoded as a character.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So
          someone who wants to send the message "It is snowing." can
          look up the character, maybe from a printed list, or in a menu
          in an email program, and send it in an email to a friend.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">The
          friend can then find the meaning of the character, or a
          computer system can decode it automatically, and the message
          "It is snowing." becomes known to the friend.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Yes,
          it could be done, but it is not of any use.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">I
          then realized that the decoding by or for the friend need not
          be into the same language, so the received message could have
          gone ("tunneled") through the language barrier.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Oh!</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So
          the encoded character was a localizable sentence.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Not
          localized. But localizable.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So
          the significance of what I am suggesting is that the
          localization is at the receiving end of a communication, not
          at the sending end.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So
          in the scenario that is in the slide show, the link repeated
          here for convenience,</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <a target="_blank" rel="noopener noreferrer"
href="http://www.users.globalnet.co.uk/~ngo/slide_show_about_localizable_sentences.pdf"
          moz-do-not-send="true"><span
            style="font-family:Arial, sans-serif;font-size:18px;">http://www.users.globalnet.co.uk/~ngo/slide_show_about_localizable_sentences.pdf</span></a></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Albert
          does not need to know the language in which Sonja works.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Extending
          the simulation, Sonja can be sending out localizable emails to
          various people in various countries and upon receipt each
          email is localized into the language being used by the person
          at that location.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">So
          this suggestion is based on my opinion that that would be good
          to be able to do. I do not know if it can already be done.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">The
          only system of which I am aware that uses code numbers that
          can be used to send precise information through the language
          barrier is SNOMED CT a clinical terminology system, though the
          code numbers are not only for that purpose, they are used for
          accurate recording of clinical records within a country.</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">William
          Overington</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span><br>
        <span style="font-family:Arial, sans-serif;font-size:18px;">Tuesday
          1 October 2024</span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span></p>
      <p><span style="font-family:Arial, sans-serif;font-size:18px;"> </span></p>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
mpeg-otspec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>
<a class="moz-txt-link-freetext" href="https://lists.aau.at/mailman/listinfo/mpeg-otspec">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 

John Hudson
Tiro Typeworks Ltd    <a class="moz-txt-link-abbreviated" href="http://www.tiro.com">www.tiro.com</a>

Tiro Typeworks is physically located on islands 
in the Salish Sea, on the traditional territory 
of the Snuneymuxw and Penelakut First Nations.

__________

EMAIL HOUR
In the interests of productivity, I am only dealing 
with email towards the end of the day, typically 
between 4PM and 5PM. If you need to contact me more 
urgently, please use other means.</pre>
  </body>
</html>