Others [Translation Request] The Encyclopedia of Tentacles for Boys Vol.1

Succubus Hunter

Conversation Conqueror
May 19, 2020
7,661
14,751
Unfortunately, I think the last attempt hit a brick wall, at least it sounded that way. According to Ophanim the coding is too specific, that just so few people are able to work with it. And I don't know if he's still trying out jackalo's hint, or gave up on it for the time being.

Btw., you seem to show up in every thread that I follow and that are quite a few, even on hemdom blog, nice taste. ;)
Darn, it's too bad about the coding. There are not nearly enough games where males get taken by tentacles. I hope someone makes a POV one for the community to play.

Thank you for the complement, you are the first person to mention seeing me on Hemdomblog as well. I love both of these sites and am glad to participate in these forums.
 

Enoz56F

New Member
Jul 28, 2020
11
29
The problem is, if you try to translate stuff into a language with spaces between words, the space characters will randomly disappear, jamming words together into a blob of 3-4 words apiece (Japanese font issues, perhaps?). I looked into this one while cooling down from working on my current project, and I honestly have no idea where to look to work out what the text encoding issue is.
I was bored and randomly decided to look into this; I played around with the code file a little, and after a moment of epiphany I think I figured it out, actually. I still don't really know why it happens (I have a theory, but I really don't know), but I'm pretty sure I know what happens.

So, it looks like the software treats 2 western characters as one character block (my theory is that japanese characters are done with 2 byte per character, while the latin alphabet only uses 1?). So what happens is that when you have the whitespace at the end of a character block, it renders properly. But any (even multiple) whitespace at the beginning of a block will be ignored by the software, for some reason.

So, e.g. the string "1 2 3 45 6 7 89 0", is turned into 1 |2 |3 |45| 6 |7 |89| 0
This then renders as "1 2 3 456 7 89". The space in front of the 6 is kicked out because it's at the beginning of the block (instead the block is then the "6 "). Similarly the space after the 9 is kicked out, and the 0 is not displayed, because it's only half a block.

Additional whitespaces are also ignored, so "1 23 4 5 " also turns into "1 234 5 ".

This is, I believe, also why sometimes a string cuts off one letter short. If the used string has an odd number of letters, the last letter will be swallowed by the program because it's only "half a block". This one can be fixed by adding a whitespace to the string, therefore "completing" the final block.

The solution I have found is probably not elegant, but it works. Effectively: After any word (word being a continuous string of characters between two whitespaces or a whitespace and the beginning/end of the string) with odd letters, you have to put a space (even/especially if it's the last word in the string). After any word with even letters, you instead put the japanese whitespace ( ). It's a bit wider than the regular space, so the word spacing is going to look a bit wobbly, but because it's a proper japanese character, it's worth a whole block and therefore "resets" the splitting of the sentence, so that the next block will begin with the first letter of the next word.

Note: this is also the issue why sometimes the program adds a weird @. if you only use the japanese space symbol: if you place it after an odd word, you break the 2 bytes of the japanese character up into two blocks "hello world" becomes he|ll|o@|.w|or|ld.

Now, I don't actually speak japanese, so I couldn't translate it myself, but I added a proof-of-concept picture here regarding the possible final result. The english there is roughly taken Google Translate.
leech_tl_poc.png

Edit: And now I realized I missed the whole 3rd page where a bunch of other people already solved the issue. Now I feel bad. :(
 
Last edited:

Succubus Hunter

Conversation Conqueror
May 19, 2020
7,661
14,751
I was bored and randomly decided to look into this; I played around with the code file a little, and after a moment of epiphany I think I figured it out, actually. I still don't really know why it happens (I have a theory, but I really don't know), but I'm pretty sure I know what happens.

So, it looks like the software treats 2 western characters as one character block (my theory is that japanese characters are done with 2 byte per character, while the latin alphabet only uses 1?). So what happens is that when you have the whitespace at the end of a character block, it renders properly. But any (even multiple) whitespace at the beginning of a block will be ignored by the software, for some reason.

So, e.g. the string "1 2 3 45 6 7 89 0", is turned into 1 |2 |3 |45| 6 |7 |89| 0
This then renders as "1 2 3 456 7 89". The space in front of the 6 is kicked out because it's at the beginning of the block (instead the block is then the "6 "). Similarly the space after the 9 is kicked out, and the 0 is not displayed, because it's only half a block.

Additional whitespaces are also ignored, so "1 23 4 5 " also turns into "1 234 5 ".

This is, I believe, also why sometimes a string cuts off one letter short. If the used string has an odd number of letters, the last letter will be swallowed by the program because it's only "half a block". This one can be fixed by adding a whitespace to the string, therefore "completing" the final block.

The solution I have found is probably not elegant, but it works. Effectively: After any word (word being a continuous string of characters between two whitespaces or a whitespace and the beginning/end of the string) with odd letters, you have to put a space (even/especially if it's the last word in the string). After any word with even letters, you instead put the japanese whitespace ( ). It's a bit wider than the regular space, so the word spacing is going to look a bit wobbly, but because it's a proper japanese character, it's worth a whole block and therefore "resets" the splitting of the sentence, so that the next block will begin with the first letter of the next word.

Note: this is also the issue why sometimes the program adds a weird @. if you only use the japanese space symbol: if you place it after an odd word, you break the 2 bytes of the japanese character up into two blocks "hello world" becomes he|ll|o@|.w|or|ld.

Now, I don't actually speak japanese, so I couldn't translate it myself, but I added a proof-of-concept picture here regarding the possible final result. The english there is roughly taken Google Translate.
View attachment 1055667

Edit: And now I realized I missed the whole 3rd page where a bunch of other people already solved the issue. Now I feel bad. :(
The issue may have already been solved but big kudos to you for taking the time to help.
 
  • Like
Reactions: bwardyunbip

Peredine

Newbie
Mar 10, 2018
73
117
Now, I don't actually speak japanese, so I couldn't translate it myself, but I added a proof-of-concept picture here regarding the possible final result. The english there is roughly taken Google Translate.
View attachment 1055667

Edit: And now I realized I missed the whole 3rd page where a bunch of other people already solved the issue. Now I feel bad. :(
I strongly recommend using DeepL for machine translation, it's very very good, even for porn games!

Oh I'm still grateful that you're helping my man!
 
Jan 8, 2019
103
46
2 questions:
1- The game only has a gallery? because the first button send me to gallery and second is for ¿load? i suppose.
2- how i attach all volumens in one?
 

Peredine

Newbie
Mar 10, 2018
73
117
Yes, it's a very short story gallery "game"
You need to extract the files from volume 2 and 3 into volume 1.
 

ArzorX

Newbie
Sep 2, 2019
51
45
I was bored and randomly decided to look into this; I played around with the code file a little, and after a moment of epiphany I think I figured it out, actually. I still don't really know why it happens (I have a theory, but I really don't know), but I'm pretty sure I know what happens.

So, it looks like the software treats 2 western characters as one character block (my theory is that japanese characters are done with 2 byte per character, while the latin alphabet only uses 1?). So what happens is that when you have the whitespace at the end of a character block, it renders properly. But any (even multiple) whitespace at the beginning of a block will be ignored by the software, for some reason.

So, e.g. the string "1 2 3 45 6 7 89 0", is turned into 1 |2 |3 |45| 6 |7 |89| 0
This then renders as "1 2 3 456 7 89". The space in front of the 6 is kicked out because it's at the beginning of the block (instead the block is then the "6 "). Similarly the space after the 9 is kicked out, and the 0 is not displayed, because it's only half a block.

Additional whitespaces are also ignored, so "1 23 4 5 " also turns into "1 234 5 ".

This is, I believe, also why sometimes a string cuts off one letter short. If the used string has an odd number of letters, the last letter will be swallowed by the program because it's only "half a block". This one can be fixed by adding a whitespace to the string, therefore "completing" the final block.

The solution I have found is probably not elegant, but it works. Effectively: After any word (word being a continuous string of characters between two whitespaces or a whitespace and the beginning/end of the string) with odd letters, you have to put a space (even/especially if it's the last word in the string). After any word with even letters, you instead put the japanese whitespace ( ). It's a bit wider than the regular space, so the word spacing is going to look a bit wobbly, but because it's a proper japanese character, it's worth a whole block and therefore "resets" the splitting of the sentence, so that the next block will begin with the first letter of the next word.

Note: this is also the issue why sometimes the program adds a weird @. if you only use the japanese space symbol: if you place it after an odd word, you break the 2 bytes of the japanese character up into two blocks "hello world" becomes he|ll|o@|.w|or|ld.

Now, I don't actually speak japanese, so I couldn't translate it myself, but I added a proof-of-concept picture here regarding the possible final result. The english there is roughly taken Google Translate.
View attachment 1055667

Edit: And now I realized I missed the whole 3rd page where a bunch of other people already solved the issue. Now I feel bad. :(
Hmmmmm, thanks for the info maybe with this I could do something else...
 
  • Like
Reactions: cheekypig55