X-Git-Url: https://git.stg.codes/stg.git/blobdiff_plain/0c9c28efcd43f53ac54aa60b2dfefa69c70dbadf..6b6d9b29e9e9e91f79507a8bf193fb30de311dcc:/doc/help/xslt/params/man.break.after.slash.xml diff --git a/doc/help/xslt/params/man.break.after.slash.xml b/doc/help/xslt/params/man.break.after.slash.xml new file mode 100644 index 00000000..859edb73 --- /dev/null +++ b/doc/help/xslt/params/man.break.after.slash.xml @@ -0,0 +1,46 @@ + + +man.break.after.slash +boolean + + +man.break.after.slash +Enable line-breaking after slashes? + + + + +0 + + +Description + +If non-zero, line-breaking after slashes is enabled. This is +mainly useful for causing long URLs or pathnames/filenames to be +broken up or "wrapped" across lines (though it also has the side +effect of sometimes causing relatively short URLs and pathnames to be +broken up across lines too). + +If zero (the default), line-breaking after slashes is +disabled. In that case, strings containing slashes (for example, URLs +or filenames) are not broken across lines, even if they exceed the +maximum column widith. + + + If you set a non-zero value for this parameter, check your + man-page output carefuly afterwards, in order to make sure that the + setting has not introduced an excessive amount of breaking-up of URLs + or pathnames. If your content contains mostly short URLs or + pathnames, setting a non-zero value for + man.break.after.slash will probably result in + in a significant number of relatively short URLs and pathnames being + broken across lines, which is probably not what you want. + + + +