<refentry xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:src="http://nwalsh.com/xmlns/litprog/fragment" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="5.0" xml:id="man.hyphenate.filenames"> <refmeta> <refentrytitle>man.hyphenate.filenames</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>man.hyphenate.filenames</refname> <refpurpose>Hyphenate filenames?</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.hyphenate.filenames.frag"> <xsl:param name="man.hyphenate.filenames">0</xsl:param></src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>If zero (the default), hyphenation is suppressed for <tag>filename</tag> output.</para> <note> <para>If hyphenation is already turned off globally (that is, if <parameter>man.hyphenate</parameter> is zero, setting <parameter>man.hyphenate.filenames</parameter> is not necessary.</para> </note> <para>If <parameter>man.hyphenate.filenames</parameter> is non-zero, filenames will not be treated specially and are subject to hyphenation just like other words.</para> <note> <para>If you are thinking about setting a non-zero value for <parameter>man.hyphenate.filenames</parameter> in order to make long filenames/pathnames break across lines, you'd probably be better off experimenting with setting the <parameter>man.break.after.slash</parameter> parameter first. That will cause long pathnames to be broken after slashes.</para> </note> </refsection> </refentry>