Image 1 is a showcase of what I'm talking about.
Image 2 assumes the whole image is the selection area.
I recreated it since it doesn't show up in screenshots.
This was done in the auto mode.
Its probably to do with them being combined into a paragraph, but even if they are a combined paragraph, this doesn't seem intended and should probably line break if it goes past the original text boundaries.
Ah, okay, I see what you're talking about now. At least in image 1, not sure if image 2 is what you intended to show me?
So. I could fix the issue that crops up here in image 1, however, creating a rule that fixes this exact edge case may break another format of text. It's really hard to tell, but I've been through enough of these battles now to know that it isn't unlikely to happen. You fix one thing, and sure enough, a few minutes, hours or days later you realize that the fix did its job but the cost of it was that another type of text format got completely screwed up in the process.
I am in the process of creating an automated testing tool for this exact purpose. It will take a while longer yet to finish, but when it's done, it will speed up the process of testing by orders of magnitude and make me much less likely to break anything when creating new rules/algorithms.
Is this specific problem something that you find annoying enough that it bothers you? Rest assured, I don't want it to look like that either, but I can't promise that I'll get it fixed this week (due to what I wrote above). In the meantime, I would recommend trying to make your selections less wide.
Thank you! :)
Image 2 is just an example of the same thing without the fancy boxes and text(the text is suppose to be bullet points but juts out)
But yeah honestly I don't really care about this problem specifically, and just changing the settings for detecting paragraphs lets you mostly get rid of it if it does bother someone.
Ah, I see it now, sorry haha. It's 1:30am here, I'm tired.
Mmh. It is difficult to judge exactly how people tend to use the different mode. Me personally would be selecting smaller areas when I am using it, hence the issue never really shows up. But I reckon a great deal of people are selecting big areas like that.
I'll have a quick look at it tomorrow, at the moment I can't think of anything it could break to fix this issue.
What about vertical text? How often would you be trying to capture that in your case? Would it be on the web or do you play any games with vertical text? :)
jp text tends to only be vertical in specific situations and they aren't very common in games, but quite very common in things like manga which is what I was testing it on;
Which is where the auto mode would be useful since you could just select the whole page, because selecting specific text boxes in that sort of context would be very time consuming.
Gotcha! That is for sure something I'd like to support. Obviously GameTranslate is catered to games, but I'd like to support as many scenarios as possible.
I'll have to think about how this could be implemented. It would probably have to be its own mode entirely. If you want the target language to be written out horizontally, I would have to make it be somewhat of a mix of manual and automatic mode.
Thank you!
I'm not very familiar with Manga, but if most have a text layout similar to this image;
Then I believe we for sure could get away with just making the non-JP text slightly smaller and still keep it within the bounds of the chat bubble. I'm intrigued to solve this so you may see it solved soon (I hope!).
Yup, the layout is very often in bubbles like that. Though one thing you may want to watch out for is that the text in the green coloured boxes should be ignored since its just giving the spelling for the red colored character.
Though sometimes there is text outside the boxes, that could be fully without a box or with a strangely shaped one. (Random image examples)
I look forward to any potential implementations that could be added. :D
