In this PR, I've implemented a version of HDTCat working whatever the input count of HDTs (for MS/4S Dictionaries), it follows the same algorithm as HDTCat_let's_make_HDT_scale, but with multiple HDT input, except that the streams from each HDT are merged to behave like one HDT
I've added it in HDTCatTree with the option loader.cattree.kcat to set the number of HDT to merge at the same time
3 options are here to describe the cat:
hdtcat.location: the build directory, by default a temporary location is specified
hdtcat.location.future: the future location of the HDT, can't be in the build directory
hdtcat.deleteLocation: if we should delete the build directory (if specified)
API
I've added all the options in the HDTOptionsKeys class
D063520
commented
1 year ago
Hello!
In this PR, I've implemented a version of HDTCat working whatever the input count of HDTs (for MS/4S Dictionaries), it follows the same algorithm as HDTCat_let's_make_HDT_scale, but with multiple HDT input, except that the streams from each HDT are merged to behave like one HDT
I've added it in HDTCatTree with the option
loader.cattree.kcatto set the number of HDT to merge at the same time3 options are here to describe the cat:
hdtcat.location: the build directory, by default a temporary location is specifiedhdtcat.location.future: the future location of the HDT, can't be in the build directoryhdtcat.deleteLocation: if we should delete the build directory (if specified)API
I've added all the options in the HDTOptionsKeys class
A new method was added in HDTManager
Using the old method will use the legacy algorithm
CLI
I've added the BATCH version of hdtCat with the
hdtCat.batI've added the -kcat argument to HDTCat to allow to use the new version of HDTCat with 2 HDTs, but now we can specify the number of HDTs we want
With hdtVerify, I've removed the limit of 1 hdt, I've added 2 arguments:
-progressto see the progress of the verify for the current HDT-equalsto see that all the HDTs specified are equalsCore
The implementation of HDTCat, with tests