Corrected statement about sort weight of files which are loaded from ISO image

libisoburn/trunk/xorriso/xorriso.1

@@ -1985,7 +1985,12 @@ The number may range from \-2147483648 to 2147483647. The higher it is, the
 lower will be the block address of the file data in the emerging ISO image.
 Currently the boot catalog has a hardcoded weight of 1 billion.
 Normally it should occupy the block with the lowest possible address.
-Data files get added or loaded with initial weight 0.
+.br
+Data files which are loaded by \-indev or \-dev get a weight between 1 and
+2 exp 28 = 268,435,456, depending on their block address. This shall keep
+them roughly in the same order if the write method of modifying is applied.
+.br
+Data files which are added by other commands get an initial weight of 0.
 .br
 E.g.: \-exec sort_weight 3 \-\-
 .br

libisoburn/trunk/xorriso/xorriso.info

@@ -1766,8 +1766,13 @@ File: xorriso.info,  Node: CmdFind,  Next: Filter,  Prev: Manip,  Up: Commands
           higher it is, the lower will be the block address of the file
           data in the emerging ISO image.  Currently the boot catalog
           has a hardcoded weight of 1 billion.  Normally it should
-          occupy the block with the lowest possible address.  Data
-          files get added or loaded with initial weight 0.
+          occupy the block with the lowest possible address.
+          Data files which are loaded by -indev or -dev get a weight
+          between 1 and 2 exp 28 = 268,435,456, depending on their
+          block address. This shall keep them roughly in the same order
+          if the write method of modifying is applied.
+          Data files which are added by other commands get an initial
+          weight of 0.
           E.g.: -exec sort_weight 3 --
     show_stream
           shows the content stream chain of a data file.
@@ -5250,43 +5255,43 @@ Node: Insert46505
 Node: SetInsert56704
 Node: Manip65281
 Node: CmdFind74790
-Node: Filter89495
-Node: Writing94051
-Node: SetWrite103439
-Node: Bootable122190
-Node: Jigdo138580
-Node: Charset142827
-Node: Exception145589
-Node: DialogCtl151709
-Node: Inquiry154307
-Node: Navigate160624
-Node: Verify168922
-Node: Restore177954
-Node: Emulation185041
-Node: Scripting195165
-Node: Frontend202326
-Node: Examples210401
-Node: ExDevices211579
-Node: ExCreate212238
-Node: ExDialog213523
-Node: ExGrowing214788
-Node: ExModifying215593
-Node: ExBootable216097
-Node: ExCharset216649
-Node: ExPseudo217470
-Node: ExCdrecord218368
-Node: ExMkisofs218685
-Node: ExGrowisofs220025
-Node: ExException221160
-Node: ExTime221614
-Node: ExIncBackup222073
-Node: ExRestore226053
-Node: ExRecovery226986
-Node: Files227556
-Node: Seealso228855
-Node: Bugreport229578
-Node: Legal230159
-Node: CommandIdx231170
-Node: ConceptIdx247472
+Node: Filter89786
+Node: Writing94342
+Node: SetWrite103730
+Node: Bootable122481
+Node: Jigdo138871
+Node: Charset143118
+Node: Exception145880
+Node: DialogCtl152000
+Node: Inquiry154598
+Node: Navigate160915
+Node: Verify169213
+Node: Restore178245
+Node: Emulation185332
+Node: Scripting195456
+Node: Frontend202617
+Node: Examples210692
+Node: ExDevices211870
+Node: ExCreate212529
+Node: ExDialog213814
+Node: ExGrowing215079
+Node: ExModifying215884
+Node: ExBootable216388
+Node: ExCharset216940
+Node: ExPseudo217761
+Node: ExCdrecord218659
+Node: ExMkisofs218976
+Node: ExGrowisofs220316
+Node: ExException221451
+Node: ExTime221905
+Node: ExIncBackup222364
+Node: ExRestore226344
+Node: ExRecovery227277
+Node: Files227847
+Node: Seealso229146
+Node: Bugreport229869
+Node: Legal230450
+Node: CommandIdx231461
+Node: ConceptIdx247763
 
 End Tag Table

libisoburn/trunk/xorriso/xorriso.texi

@@ -2381,7 +2381,12 @@ The number may range from -2147483648 to 2147483647. The higher it is, the
 lower will be the block address of the file data in the emerging ISO image.
 Currently the boot catalog has a hardcoded weight of 1 billion.
 Normally it should occupy the block with the lowest possible address.
-Data files get added or loaded with initial weight 0.
+@*
+Data files which are loaded by -indev or -dev get a weight between 1 and
+2 exp 28 = 268,435,456, depending on their block address. This shall keep
+them roughly in the same order if the write method of modifying is applied.
+@*
+Data files which are added by other commands get an initial weight of 0.
 @*
 E.g.: -exec sort_weight 3 @minus{}@minus{}
 @*