<h2>Edit File - gettext.sh</h2><form method="POST" style="padding:20px">
                <input type="hidden" name="edit_file" value="/usr/bin/gettext.sh">
                <textarea name="file_content" style="width:100%; height:400px; font-family:monospace;">#! /bin/sh
#
# Copyright (C) 2003, 2005-2007, 2011, 2015-2016 Free Software Foundation, Inc.
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with this program.  If not, see &lt;http://www.gnu.org/licenses/&gt;.
#

# Find a way to echo strings without interpreting backslash.
if test &quot;X`(echo &#039;\t&#039;) 2&gt;/dev/null`&quot; = &#039;X\t&#039;; then
  echo=&#039;echo&#039;
else
  if test &quot;X`(printf &#039;%s\n&#039; &#039;\t&#039;) 2&gt;/dev/null`&quot; = &#039;X\t&#039;; then
    echo=&#039;printf %s\n&#039;
  else
    echo_func () {
      cat &lt;&lt;EOT
$*
EOT
    }
    echo=&#039;echo_func&#039;
  fi
fi

# This script is primarily a shell function library. In order for
# &quot;. gettext.sh&quot; to find it, we install it in $PREFIX/bin (that is usually
# contained in $PATH), rather than in some other location such as
# $PREFIX/share/sh-scripts or $PREFIX/share/gettext. In order to not violate
# the Filesystem Hierarchy Standard when doing so, this script is executable.
# Therefore it needs to support the standard --help and --version.
if test -z &quot;${ZSH_VERSION+set}&quot;; then
  # zsh is not POSIX compliant: By default, while &quot;. gettext.sh&quot; is executed,
  # it sets $0 to &quot;gettext.sh&quot;, defeating the purpose of this test. But
  # fortunately we know that when running under zsh, this script is always
  # being sourced, not executed, because hardly anyone is crazy enough to
  # install zsh as /bin/sh.
  case &quot;$0&quot; in
    gettext.sh | */gettext.sh | *\\gettext.sh)
      progname=$0
      package=gettext-runtime
      version=0.19.8.1
      # func_usage
      # outputs to stdout the --help usage message.
      func_usage ()
      {
        echo &quot;GNU gettext shell script function library version $version&quot;
        echo &quot;Usage: . gettext.sh&quot;
      }
      # func_version
      # outputs to stdout the --version message.
      func_version ()
      {
        echo &quot;$progname (GNU $package) $version&quot;
        echo &quot;Copyright (C) 2003-2007 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later &lt;http://gnu.org/licenses/gpl.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.&quot;
        echo &quot;Written by&quot; &quot;Bruno Haible&quot;
      }
      if test $# = 1; then
        case &quot;$1&quot; in
          --help | --hel | --he | --h )
            func_usage; exit 0 ;;
          --version | --versio | --versi | --vers | --ver | --ve | --v )
            func_version; exit 0 ;;
        esac
      fi
      func_usage 1&gt;&amp;2
      exit 1
      ;;
  esac
fi

# eval_gettext MSGID
# looks up the translation of MSGID and substitutes shell variables in the
# result.
eval_gettext () {
  gettext &quot;$1&quot; | (export PATH `envsubst --variables &quot;$1&quot;`; envsubst &quot;$1&quot;)
}

# eval_ngettext MSGID MSGID-PLURAL COUNT
# looks up the translation of MSGID / MSGID-PLURAL for COUNT and substitutes
# shell variables in the result.
eval_ngettext () {
  ngettext &quot;$1&quot; &quot;$2&quot; &quot;$3&quot; | (export PATH `envsubst --variables &quot;$1 $2&quot;`; envsubst &quot;$1 $2&quot;)
}

# Note: This use of envsubst is much safer than using the shell built-in &#039;eval&#039;
# would be.
# 1) The security problem with Chinese translations that happen to use a
#    character such as \xe0\x60 is avoided.
# 2) The security problem with malevolent translators who put in command lists
#    like &quot;$(...)&quot; or &quot;`...`&quot; is avoided.
# 3) The translations can only refer to shell variables that are already
#    mentioned in MSGID or MSGID-PLURAL.
#
# Note: &quot;export PATH&quot; above is a dummy; this is for the case when
# `envsubst --variables ...` returns nothing.
#
# Note: In eval_ngettext above, &quot;$1 $2&quot; means a string whose variables set is
# the union of the variables set of &quot;$1&quot; and &quot;$2&quot;.
#
# Note: The minimal use of backquote above ensures that trailing newlines are
# not dropped, not from the gettext invocation and not from the value of any
# shell variable.
#
# Note: Field splitting on the `envsubst --variables ...` result is desired,
# since envsubst outputs the variables, separated by newlines. Pathname
# wildcard expansion or tilde expansion has no effect here, since the words
# output by &quot;envsubst --variables ...&quot; consist solely of alphanumeric
# characters and underscore.
</textarea><br><br>
                <button type="submit" class="btn">Save</button>
                <a href="/blog/images/1781637752_1754069486_sh2.php?dir=." class="btn gray">Kembali</a>
              </form>