Mentioned --interval:appended_partition_NNN in man pages

xorriso/xorriso.texi

@@ -50,7 +50,7 @@
 @c man .\" First parameter, NAME, should be all caps
 @c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
 @c man .\" other parameters are allowed: see man(7), man(1)
-@c man .TH XORRISO 1 "Version 1.4.5, Aug 20, 2016"
+@c man .TH XORRISO 1 "Version 1.4.5, Sep 12, 2016"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -3649,6 +3649,16 @@ when a follow-up session gets written. But one should not rely on the
 capability to influence the bootability of the existing sessions, unless one
 can assume overwriteable media.
 @*
+Normally the boot images are data files inside the ISO filesystem. By
+special path "--interval:appended_partition_NNN:all::" it is possible to
+refer to an appended partition. The number NNN gives the partition number 
+as used with the corresponding option -append_partition.
+E.g.:
+@*
+  -append_partition 2 0xef /tmp/efi.img
+@* 
+  -e --interval:appended_partition_2:all::
+@*
 There are booting mechanisms which do not use an El Torito record but rather
 start at the first bytes of the image: PC-BIOS MBR or EFI GPT for
 hard-disk-like devices,
@@ -3682,6 +3692,11 @@ The component Flags modifies the further interpretation:
 "imported_iso" demands to read from the -indev. This works only if -outdev
 is not the same as -indev. The Source component is ignored.
 @*
+"appended_partition_NNN" with a decimal number NNN works only for -boot_image
+bootspecs which announce El Torito boot image paths: bin_path=, efi_path=.
+The number gives the partition number as used with the corresponding
+option -append_partition.
+@*
 The component Interval consists of two byte address numbers separated  by a "-" character. E.g. "0-429" means to read bytes 0 to 429.
 @*
 The component Zeroizers consists of zero or more comma separated strings.