<?xml version="1.0" ?>
<?xml-stylesheet type='text/xsl' href='../resources/feed.xsl'?>
<interface uri="http://repo.roscidus.com/devel/gettext" xmlns="http://zero-install.sourceforge.net/2004/injector/interface" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://zero-install.sourceforge.net/2004/injector/interface http://0install.de/schema/injector/interface/interface.xsd http://0install.de/schema/desktop-integration/capabilities http://0install.de/schema/desktop-integration/capabilities/capabilities.xsd">
  <replaced-by interface="https://apps.0install.net/devel/gettext.xml"/>
  <feed src="https://apps.0install.net/devel/gettext.xml"/>
  <name>GetText</name>
  <summary xml:lang="en">GetText: library and tools for native language support</summary>
  <description xml:lang="en">A well integrated set of tools and documentation to help programmers, translators, and users make other GNU packages produce multi-lingual messages. The tools include a set of conventions about how programs should be written to support message catalogs, a directory and file naming organzation for those message catalogs, a runtime library that supports retrieval of translated messages, and a few stand-alone programs to manipulate sets of strings. A special GNU Emacs mode also helps work with these strings. 

Libintl is a library that provides native language support to programs. It is part of Gettext. 
•LibIntl-1 is in Gettext-0.10-.. 
•LibIntl-2 is in Libintl-0.11-.. 
•LibIntl-3 is in LibIntl-0.14-.. and in Gettext-0.14-.. 
</description>
  <icon href="https://raw.githubusercontent.com/0install/0install.de-feeds/master/Gow.ico" type="image/vnd.microsoft.icon"/>
  <icon href="https://raw.githubusercontent.com/0install/0install.de-feeds/master/Gow.png" type="image/png"/>
  <category>Development</category>
  <homepage>http://gnuwin32.sourceforge.net/packages/gettext.htm</homepage>
  <needs-terminal/>
  <entry-point binary-name="gettext" command="run">
    <needs-terminal/>
    <name xml:lang="en">gettext</name>
    <summary xml:lang="en">translate message</summary>
    <description xml:lang="en">The  gettext  program translates a natural language mes-
       sage into the user's language, by looking up the  trans-
       lation in a message catalog.</description>
  </entry-point>
  <entry-point binary-name="envsubst" command="envsubst">
    <needs-terminal/>
    <name xml:lang="en">envsubst</name>
    <summary xml:lang="en">substitutes  environment variables in shell</summary>
    <description xml:lang="en">Substitutes the values of environment variables.</description>
  </entry-point>
  <entry-point binary-name="hostname" command="hostname">
    <needs-terminal/>
    <summary xml:lang="en">Print the machine's hostname.</summary>
  </entry-point>
  <entry-point binary-name="msgattrib" command="msgattrib">
    <needs-terminal/>
    <summary xml:lang="en">Filters the messages of a translation catalog according to their attributes,</summary>
  </entry-point>
  <entry-point binary-name="msgcat" command="msgcat">
    <needs-terminal/>
    <summary xml:lang="en">Concatenates and merges the specified PO files.</summary>
    <description xml:lang="en">By using the --more-than option, greater commonality may be requested
before messages are printed.  Conversely, the --less-than option may be
used to specify less commonality before messages are printed (i.e.
--less-than=2 will only print the unique messages).  Translations,
comments and extract comments will be cumulated, except that if --use-first
is specified, they will be taken from the first PO file to define them.
File positions from all PO files will be cumulated.</description>
  </entry-point>
  <entry-point binary-name="msgcmp" command="msgcmp">
    <needs-terminal/>
    <summary xml:lang="en">Compare two Uniforum style .po files to check that both contain the same</summary>
    <description xml:lang="en">The def.po file is an existing PO file with the
translations.  The ref.pot file is the last created PO file, or a PO Template
file (generally created by xgettext).  This is useful for checking that
you have translated each and every message in your program.  Where an exact
match cannot be found, fuzzy matching is used to produce better diagnostics.</description>
  </entry-point>
  <entry-point binary-name="msgcomm" command="msgcomm">
    <needs-terminal/>
    <summary xml:lang="en">Find messages which are common to two or more of the specified PO files.</summary>
    <description xml:lang="en">By using the --more-than option, greater commonality may be requested
before messages are printed.  Conversely, the --less-than option may be
used to specify less commonality before messages are printed (i.e.
--less-than=2 will only print the unique messages).  Translations,
comments and extract comments will be preserved, but only from the first
PO file to define them.  File positions from all PO files will be
cumulated.</description>
  </entry-point>
  <entry-point binary-name="msgconv" command="msgconv">
    <needs-terminal/>
    <summary xml:lang="en">Converts a translation catalog to a different character encoding.</summary>
  </entry-point>
  <entry-point binary-name="msgen" command="msgen">
    <needs-terminal/>
    <summary xml:lang="en">Creates an English translation catalog.  </summary>
    <description xml:lang="en">The input file is the last created English PO file, or a PO Template file (generally created by
xgettext).  Untranslated entries are assigned a translation that is
identical to the msgid.</description>
  </entry-point>
  <entry-point binary-name="msgexec" command="msgexec">
    <needs-terminal/>
    <summary xml:lang="en">Applies a command to all translations of a translation catalog.</summary>
    <description xml:lang="en">The COMMAND can be any program that reads a translation from standard
input.  It is invoked once for each translation.  Its output becomes
msgexec's output.  msgexec's return code is the maximum return code
across all invocations.</description>
  </entry-point>
  <entry-point binary-name="msgfilter" command="msgfilter">
    <needs-terminal/>
    <summary xml:lang="en">edit translations of message catalog</summary>
    <description xml:lang="en">Applies a filter to all translations of a translation catalog.</description>
  </entry-point>
  <entry-point binary-name="msgfmt" command="msgfmt">
    <needs-terminal/>
    <summary xml:lang="en">Generate binary message catalog from textual translation description.</summary>
  </entry-point>
  <entry-point binary-name="msggrep" command="msggrep">
    <needs-terminal/>
    <summary xml:lang="en">Extracts all messages of a translation catalog that match a given pattern</summary>
  </entry-point>
  <entry-point binary-name="msginit" command="msginit">
    <needs-terminal/>
    <summary xml:lang="en">Creates a new PO file, initializing the meta information with values from the</summary>
  </entry-point>
  <entry-point binary-name="msgmerge" command="msgmerge">
    <needs-terminal/>
    <summary xml:lang="en">Merges two Uniforum style .po files together.</summary>
    <description xml:lang="en">The def.po file is an
existing PO file with translations which will be taken over to the newly
created file as long as they still match; comments will be preserved,
but extracted comments and file positions will be discarded.  The ref.pot
file is the last created PO file with up-to-date source references but
old translations, or a PO Template file (generally created by xgettext);
any translations or comments in the file will be discarded, however dot
comments and file positions will be preserved.  Where an exact match
cannot be found, fuzzy matching is used to produce better results.</description>
  </entry-point>
  <entry-point binary-name="msgunfmt" command="msgunfmt">
    <needs-terminal/>
    <summary xml:lang="en">Convert binary message catalog to Uniforum style .po file.</summary>
  </entry-point>
  <entry-point binary-name="msguniq" command="msguniq">
    <needs-terminal/>
    <summary xml:lang="en">Unifies duplicate translations in a translation catalog.</summary>
    <description xml:lang="en">Finds duplicate translations of the same message ID.  Such duplicates are
invalid input for other programs like msgfmt, msgmerge or msgcat.  By
default, duplicates are merged together.  When using the --repeated option,
only duplicates are output, and all other messages are discarded.  Comments
and extracted comments will be cumulated, except that if --use-first is
specified, they will be taken from the first translation.  File positions
will be cumulated.  When using the --unique option, duplicates are discarded.</description>
  </entry-point>
  <entry-point binary-name="ngettext" command="ngettext">
    <needs-terminal/>
    <summary xml:lang="en">translate message and choose plural form</summary>
    <description xml:lang="en">The  ngettext program translates a natural language mes-
       sage into the user's language, by looking up the  trans-
       lation in a message catalog, and chooses the appropriate
       plural form, which depends on the number COUNT  and  the
       language  of  the  message catalog where the translation
       was found.</description>
  </entry-point>
  <entry-point binary-name="urlget" command="urlget">
    <needs-terminal/>
    <summary xml:lang="en">Fetches and outputs the contents of an URL.</summary>
    <description xml:lang="en">If the URL cannot be accessed,
the locally accessible FILE is used instead.</description>
  </entry-point>
  <entry-point binary-name="xgettext" command="xgettext">
    <needs-terminal/>
    <summary xml:lang="en">extract gettext strings from source</summary>
    <description xml:lang="en"> Extract translatable strings from given input files.</description>
  </entry-point>
  <entry-point binary-name="msginit" command="msginit">
    <needs-terminal/>
    <summary xml:lang="en">initialize a message catalog</summary>
    <description xml:lang="en">Creates a new PO file, initializing the meta information with values from the
user's environment.</description>
  </entry-point>
  <entry-point binary-name="msgen" command="msgen">
    <needs-terminal/>
    <summary xml:lang="en">create English message catalog</summary>
    <description xml:lang="en">Creates an English translation catalog.  The input file is the last
created English PO file, or a PO Template file (generally created by
xgettext).  Untranslated entries are assigned a translation that is
identical to the msgid.</description>
  </entry-point>
</interface>
<!-- Base64 Signature
iQEcBAABAgAGBQJf3g6zAAoJECLqERp+QkKkyIcH/i4xc68PzWwdeWV/raBbBPdAeQz92UOrrfwO
m3D1SGJNKVQu1Oam50WFoJFe4iRgh9eYWgRnH3oXMMhwSoySc7dTfXi5YlN+P/WNbLA7YBypMxn5
Qfp8OzoT4muO1dXQ3AR9IQURknGsHiyuDKTpoIye32ToutM+UEAKX5aI46Bvn9y6wnqUsQWH5K4l
/Dz5P0HJdXKr5L5Y8vpILBgrDKyqVGsxmwAGAgJJaxHaZWO97hFQGHvM0X45XRaltFCsopI2n6tn
YwMEaQo/Fm8958Ohphkvukf9to5lfZ/4gITO/a/0k3CxhMNjy7MqSyP2SCq2q9MA8Bfze2cpvtMC
tcE=

-->
