- Dec 29, 2017
- 3,181
- 5,505
While working on a major update I noticed that the "return to default" button in the SLR options menu doesn't work.
It actually breaks the translator.
Please do not use that button until I've fixed it.
I think for now I'm just going to remove large parts of that menu, because It's pretty bad in general.
Editing the files directly is actually way more comfortable than that cramped menu.
It actually breaks the translator.
Please do not use that button until I've fixed it.
I think for now I'm just going to remove large parts of that menu, because It's pretty bad in general.
Editing the files directly is actually way more comfortable than that cramped menu.
- Dec 29, 2017
- 3,181
- 5,505
I've released v1.054.
The "why on earth didn't I do this sooner" update.
Over 1000 lines of code changed.
Translation quality for multiline plugins significantly improved.
Please delete your Appdata profile folder for the last time.
(At least it "shouldn't" be required on future updates anymore.)
The "why on earth didn't I do this sooner" update.
Over 1000 lines of code changed.
Translation quality for multiline plugins significantly improved.
Please delete your Appdata profile folder for the last time.
(At least it "shouldn't" be required on future updates anymore.)
- Dec 29, 2017
- 3,181
- 5,505
- Dec 29, 2017
- 3,181
- 5,505
I've released v1.059.
Main change is that placeholders will now by default be %1 %2 %3 etc., instead of %A %B %C etc and get spaces around them.
That seems like a bad idea because it makes detecting errors harder and might leave additional spaces in text, but Sugoi seems to completely leave those alone now, which fixes quite a lot of situations in which placeholders were lost.
(Both can be changed in the options menu.)
Main change is that placeholders will now by default be %1 %2 %3 etc., instead of %A %B %C etc and get spaces around them.
That seems like a bad idea because it makes detecting errors harder and might leave additional spaces in text, but Sugoi seems to completely leave those alone now, which fixes quite a lot of situations in which placeholders were lost.
(Both can be changed in the options menu.)
Hello, I just had a few questions about how you got your SLR Translator to work and about things in the Repackage.
First, to run a working SugoiV4 server locally, you have to click and run the "activateOfflineTranslationServer.bat" file, correct?
Second, as a NVIDIA user with more than 8GB of RAM, do I extract "Sugoi-Repackage-CUDA.2024-05-21.7z" or "Sugoi-Repackage-CUDA-Full.2024-05-20.7z" with 7-zip? Also, should I use Fairseq or CTranslate2?
Lastly, in the Sugoi Toolkit V8.0, there in an "Instructions" folder with a "Basic Guide" text file. In it, there is a line that reads "For offline mode, I replace the big model (2.5GB) with the base model (900MB) so the program is lighter." Is the Sugoi Repackage related to this and should I replace the current basic model with the big model? Are the benefits to doing so?
I apologize for this long post! I am just a bit unfamiliar with these more technical setups and was just looking for a bit of clarification!
Last edited:
- Jan 12, 2020
- 149
- 422
Moadsnake004 For questions regarding the repackage, please post them in the
You must be registered to see the links
, or the Sugoi thread. I answered your question here.
- Jun 26, 2020
- 23
- 4
- Dec 29, 2017
- 3,181
- 5,505
Please compare it with the original cell.
UKNOWNCOMMAND3 usually means the escaper fucked up, "\something" was sent to sugoi, and then it ended up broken like "\some's thing".
Essentially the error system just looks for irregularities in the cell using regex patterns.
It might be completely fine, but you have to compare the cell with the original one if it looks like it makes sense or not.
In this specific case (not knowing the original cell) I would guess that one of the \n linebreaks got eaten and only the \ was left over.
Because the "m" suggests that it looked at "\I'm" and detected "\I'" as an irregular command.
\n escaping will be improved in 1.063, I'm working on a better system for that.
Edit:
Escaping \n is not as easy as it seems because RPGM also uses \n[number] and \n<text>, and so I can't just escape all \n on it's own or it will split the RPGM name stuff.
I need to escape them based on context.
It's already doing that, but it's currently somewhat unreliable when there's a lot of them.
Last edited:
- Jan 12, 2020
- 149
- 422
What context is that? Is the context determined by the code[] block number that it appears in or something else? How do you know if it is \n, \n[number], or \n<text>? Are <text> and [number] arbitrary lengths or always 1-5 characters long or some other pattern?
- Dec 29, 2017
- 3,181
- 5,505
I made that sound harder than it is, I just didn't bother to do it properly.
I just meant to check whether or not <text> or [number] exists behind the \n and if it does to escape the whole thing and not just the \n.
Essentially currently I was just grabbing everything with greedy regex patterns because lazy and stuff.
Which works "most of the time", but not always.
Now I will make separate entries instead that are executed one after another and confirm each time that there's no overlap.
Last edited:
- Jun 26, 2020
- 23
- 4
how to fix this string.trim error?? me try to unpack a exe with enigmavb then try translate use this then me got this error
- Dec 29, 2017
- 3,181
- 5,505
Huh... I've never seen that one before.
Which game are we talking about?
I would need to test that on my end.
- Jun 26, 2020
- 23
- 4