<?xml version="1.0"?>
<page id="Gimp.FileProcedure.set_format_name"
      type="topic"
      style="method"
      xmlns="http://projectmallard.org/1.0/"
      xmlns:api="http://projectmallard.org/experimental/api/"
      xmlns:ui="http://projectmallard.org/1.0/ui/">
  <info>
    <link xref="Gimp.FileProcedure" group="method" type="guide"/>
    <api:function>
      <api:returns>
        <api:type>void</api:type>
      </api:returns>
      <api:name>gimp_file_procedure_set_format_name</api:name>
      <api:arg>
        <api:type>String</api:type>
        <api:name>format_name</api:name>
      </api:arg>
    </api:function>
  </info>
  <title>Gimp.FileProcedure.prototype.set_format_name</title>
  <synopsis><code mime="text/x-gjs">
function set_format_name(format_name: String): void {
    // Gjs wrapper for gimp_file_procedure_set_format_name()
}
  </code></synopsis>
  <p>Associates a format name with a file handler procedure.</p>  <p>This name can be used for any public-facing strings, such as
graphical interface labels. An example usage would be
%GimpExportProcedureDialog title looking like "Export Image as %s".</p>  <p>Note that since the format name is public-facing, it is recommended
to localize it at runtime, for instance through gettext, like:</p>  <p>```c
gimp_file_procedure_set_format_name (procedure, _("JPEG"));
```</p>  <p>Some language would indeed localize even some technical terms or
acronyms, even if sometimes just to rewrite them with the local
writing system.</p>
  <p>Since 3.0</p>
<terms>
<item>
<title><code>format_name</code></title>
  <p>A public-facing name for the format, e.g. "PNG".</p>
</item>
</terms>

</page>
