Cumulative translation

[hleft]

Wait for how many tokens have been accumulated before starting the translation

--accumulated_num num

The strange part: I don't know how to judge how the cumulative translation results correspond to the original paragraph, so use sep = "\n\n\n\n\n", if sep="\n\n", it is often translated into the same line

A possible bug is that even if \n\n\n\n\n, it may still be translated to the same line, and then there will be problems where the translation appears, this will only affect the last num characters, after which it will return to normal

A good effect is that it can understand the context more, and the prompt is more effective

I have used various prompts before to ask it not to translate people's names, but to no avail, with context it works(It will most likely work, and in a few cases it will still translate, but it can be translated to the same name)

left:

time OPENAI_API_SYS_MSG="You are an assistant who translates computer technology books but don't translate people's names, there is a blank line after each of your translation results" python3 "make_book.py" --book_name "$filepath" --openai_key "${openai_apikey_book}" --language "zh-hans" --accumulated_num 1500

right:

time python3 "make_book.py" --book_name "$filepath" --openai_key "${openai_apikey_book}" --language "zh-hans"

[yihong0618]

Will take a look later for this PR.

[yihong0618]

the function part let me do it is OK, when I got time

[hleft]

@yihong0618 Ok, I'm trying to get a better prompt so that it can translate the same number of paragraphs as the original paragraphs, and still often have problems

[yihong0618]

@hleft FYI, I want to keep the original prompt as default because of that it costs the least tokens cc @ConanChou, most users do not care how good of all, they just want it to help them read, so users can DIY their prompt but we do not change the default one unless we found a better one better for translate and for token cost.

[hleft]

@yihong0618 I mean only modify the default prompt when --accumulated_num is enabled, because if don't modify it, you will get an error and not just a bad translation (the translated result appears in the wrong place).

[yihong0618]

yep thanks~

[hleft]

Still in testing, the current main progress is that I understand that it is not enough to just modify the prompt and retry, and some special cases must be manually handled, such as <sup>, Source: xxx link

[yihong0618]

LGTM will test and merge.
amazing work!

[zstone12]

LGTM+1.
The fantastic work!

[zstone12]

Please add the relevant content of the --accumulated_num parameter to README:D

[yihong0618]

can not test...

[yihong0618]

@hleft can this merge now?

[hleft]

@yihong0618 yes ready

[yihong0618]

please check new CI if it failed we need to fix it quick