Skip to content

Conversation

stgiga
Copy link

@stgiga stgiga commented Oct 4, 2025

Add a summary of the change(s) brought by this PR here.

UnifontEX is basically the evolved form of the Unifont TTF I contributed many years ago during the start of PC-98 support. It is quite a lot more compatible and the glyph shapes follow Unicode 15, not 2017 Unicode. AND for anyone doing stuff like Lotus Multi-Byte Character Set, DOS/V, and such, it's better. ALSO, TrueType-wise, there's more tables. I also contributed BDF and FontX2 versions because of DOSBox-X supporting those in DOS/V mode. So there is that going for it. Also of note is that this isn't the end. I'm projected to run out of codepoints when Unicode 18 or 19 drop (it depends on how many Plane 0 glyphs the latter adds), plus a year to wait for Unifont upstream to finish said release.

What issue(s) does this PR address?

It is a significant update over what was here.

If there are any related issues, reference them here. Ex. #⁠1234, Fixes #⁠1234, Closes #⁠1234, etc.

Does this PR introduce new feature(s)?

If yes, describe the feature(s) introduced.

WELL, there's a LOT more characters, and the glyph shapes are newer, and importantly, the TrueType now has a LOT of tables that improve font renderer behavior compared to what was previously there.

Does this PR introduce any breaking change(s)?

If yes, describe the breaking change(s) in detail.

Additional information

Add any additional information here.

This change is designed to make DOS/V, JEGA, FM Towns, and PC-98 support better, but it can handle WAY more than that.

stgiga and others added 7 commits December 10, 2017 14:11
This is all so that DOSBox-X can provide DOS/V support, for Japanese AND Korean. Note that I forecast up until Unicode 18-19 for when UnifontEX fills, so I may bump UnifontEX BDF and TTF until it fills.
@maron2000
Copy link
Contributor

maron2000 commented Oct 4, 2025

Great, but what are those files not related to UnifontEX?
I don't see the requirement of including np2 for Wii (18MBytes!) or those FREECG98.BMP files.

@stgiga
Copy link
Author

stgiga commented Oct 4, 2025

Great, but what are those files not related to UnifontEX? I don't see the requirement of including np2 for Wii (18MBytes!) or those FREECG98.BMP files.

Oh those are from 2017, and were used to create the first version of FREECG98 I did for DOSBox-X back then, when there was no such thing as TrueType support and an ANEX86.BMP replacement was involved. I had also thrown in that ancient UnifontEX version before it was even known as UnifontEX. So they aren't junk. I don't know why when I was in HS I included the Wii homebrew version of NP2 but it was the only version of NP2 that generates ANEX86 BMPs from TTFs that still works and on dev Dolphin it works fine. Not that i expect merging it. I just forgot to clean it out. Don't worry. Also I've been in the Discord for DOSBox-X since 2024 so I'm not a bot.

@maron2000
Copy link
Contributor

I'm not suspecting you a bot, but you have to remove the unrequired files.
You are now trying to include a bloat for all.

@maron2000
Copy link
Contributor

maron2000 commented Oct 4, 2025

By the way, I see alphabets, numbers, half-width kanas are kind of fancy in FREECG98.BMP that you included in this PR.
I don't feel its suitable for font in console.
You can see that your BMP, the characters are kind of round and is like handwriting.

Your BMP -------> Current BMP

image image

I think it is a double-byte half-width characters.
PC-98 uses slightly different glyphs for single-byte and double-byte half-width characters, so using different glyphs itself makes sense.
image

Edit: single-byte 円, 年, 月, 日, 時, 分, 秒 (characters on the right side) are fancy as well
image

@maron2000
Copy link
Contributor

The current BMP wasn't bug free.
It also had some fancy characters.

image

image

@maron2000
Copy link
Contributor

UnifontExMonoAnk.fontx2 file has some flaws in box-drawing character?

Sorry for the lots of posts. I just wanted to make things better.

image

Changing the fontxsbcs option to GONHN16X.tlf works fine.
https://web.archive.org/web/20241128212629/http://silo.la.coocan.jp/FONTV/VGON16.LZH

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants