[ ] May not need versioned folders if we don't need to read multiple versions at the same time
[ ] Add it to the alpha/beta/final publication scripts; maybe just the final one?
[ ] what else?
From KenW to PAG & RMG 20240822:
... The 14651 CTT that corresponds to the 16.0 DUCET. That is not part of UCD (or UCA for that matter), but requires special handling for 16.0. ...
We need to create a new directory: /Public/CTT/
and then populate it with: /Public/CTT/16.0.0/CTT_V16_0.txt
I have the CTT_V16_0.txt in hand. It is just the output from the last time I ran sifter, renamed per the identifier posted in Table 18 of UTS10. ...
Longer term, this is another new deliverable that presumably should be handled out of unicodetools, since that is where the sifter is going to be residing and running to produce DUCET. But figuring out how to automate that and get all the output renamed and deployed into correct directories, etc., is not something I think we should attempt for 16.0 at this point.
From KenW to PAG & RMG 20240822:
... The 14651 CTT that corresponds to the 16.0 DUCET. That is not part of UCD (or UCA for that matter), but requires special handling for 16.0. ...
We need to create a new directory: /Public/CTT/ and then populate it with: /Public/CTT/16.0.0/CTT_V16_0.txt
I have the CTT_V16_0.txt in hand. It is just the output from the last time I ran sifter, renamed per the identifier posted in Table 18 of UTS10. ...
Longer term, this is another new deliverable that presumably should be handled out of unicodetools, since that is where the sifter is going to be residing and running to produce DUCET. But figuring out how to automate that and get all the output renamed and deployed into correct directories, etc., is not something I think we should attempt for 16.0 at this point.