Help for text editing

I have been doing some testing and essentially I think you are right, I don't see any good way to make sure a poorly structured subtitle can be improved, even less when there is translation involved. Luckily I don't think we will find so many of those (I took some time looking at several subtitles from several different sources and this was just a really poor example, though useful for considering several aspects that affect the output quality).

For now, let's put that aside and consider what we already have. I am trying to make this as automatic as possible, but there is still some things to iron out.

I am currently using DeepL for most of my translation, mostly because the quality is truly above all other systems I have tested (I would say DeepL, Reverso, Google, LibreTranslate, in this order).
Regardless, all these systems have a limit on how many words/characters you can translate at a time, as well as some limitations as for file extension. DeepL requires DOCX or PDF and has a limit of 10.000 words in a single file. Currently what I do is this:

1. Run Solution 2 in original subtitle;
2. Run the PERLCODE below to divide it into chunks of X words each (unfortunately it breaks sentences midway, something I wish we could improve);
3. Manually correct the broken sentence at the end/start of each chunk;
4. Use "soffice --convert-to docx" to convert chunk files into docx format;
5. Using the browser, go to DeepL and translate the docx file into the desired language;
6. use "soffice --convert-to txt" to convert the newly translated files into txt files;
7. Manually put the chunks together (I believe this could be done with "cat", but still haven't tried it);
8. Run the awk command to put cues and translated text back together;
9. Run srtfold and (finally) get the subtitle file as intended!

So... this certainly has a lot of room for improvement. Mainly I believe awk could probably do a better job dividing the TEXT file into smaller parts while respecting entire sentences. I guess I could make it search for a period at the end of a line, but if it already exceeded the limit of words, how to make it go back? I could really use your help with this! Btw, here is the PERLCODE I have found online to do the division:

perl -e '
undef $/;
$file=<>;
while($file=~ /\G((\S+\s+){10000})/gc)
{
$i++;
open A,">","chunk-$i.txt";
print A $1;
close A;
}
$i++;
if($file=~ /\G(.+)\Z/sg)
{
open A,">","chunk-$i.txt";
print A $1;
}
'

There is also another line of code that I use when necessary. For example, I have found subtitles online that have proper punctuation and grammar, but the words are either ALL CAPS of all lower-case. In those cases, I do this:

awk '{ print tolower($0) }' subtitle.srt > newsubtitle.srt
awk ' { $0=toupper(substr($0,1,1))substr($0,2); print } ' newsubtitle.srt > yetnewsubtitle.srt

If it's an English subtitle I also run this:
sed -i "s/ i / I /g;s/i'/I'/g"

Which capitalizes "I" where necessary. It helps to make the text more visually correct. Of course names and other stuff are still wrong, but anyway I see this as an improvement over HAVING AN ALL CAPS SUBTITLE. ;)

So, to sum it all up, I would like to have a way for your Solution 2 to provide an output of X words limit per TEXT file, or if necessary maybe we could integrate that PERLCODE into it, what do you think would be easier?
Also, a more "automatic" way to get the TEXT files back into one single file that can be merged with CUES file. I think cat would do it, but we would need to integrate that at the beginning of the awk command, would that work (maybe as pipe?)?

Thanks again for the help, and apologies if this comment got a little confusing xD