Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Will the next version of GB Studio mean version 2 beta?

I thought about the Hangul block separation problem.

Korean Unicode can also input only intermediate sounds such as "ㅞ". Of course you can't type endings in this state, but if you use this you will be able to think of a way to get Hangul input from CTF without splitting Hangul blocks. However, handling characters with ending sounds is a problem.

We are going to create a Korean Ascii sprite sheet using "half-combined fonts" as shown in the image attached to the first comment.

In English, only uppercase letters remain and most special characters disappear, but it seems that only the most frequently used midtones can be carefully selected and made.

If successful, I'll share the sprite sheet and the character array.

This way, you don't have to create an algorithm to separate and combine Hangul in GlyphBoy Swap.

This is because the number of completed characters cannot exceed 256 characters, no matter how many.

If you can't separate each "letter" in a Hangul "word", there's also a way to space them one character at a time through spaces as you type.

Oh, if you really want to put spaces, you have to omit them with special characters like "-".

Not a very neat way, but sorry. I can't come up with a good idea anymore.


Sample text: 다람쥐 헌 쳇바퀴에 타고파

When entering GlyphBoy Swap: 다 람 쥐 - 헌 - 쳇 바 퀴 에 - 타 고 파


In extreme cases, if you want to type some words, you may have to use characters other than Korean.

The next version will most likely be 3.0, which is months away.

Are you going to attempt to make a sheet and array? According to toxa, one of the developers of the next version, the variable width won't change the number of available tiles, but there will be fonts, so we'll probably have even more space for characters.

Also, the problem isn't separating words, it's separating characters to their jamo. I don't understand what you mean by ommiting spaces with special characters like "-"; spaces are not the problem.