-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for non-English IBM/DOS character sets #268
Comments
For graphical ( There are many code pages, but I suppose that just a few are common, so it would be nice to have them. (I've personally run into the problem of gfxlib2 not supporting the default system codepage.) And they are LZW compressed, and there's heaps of redundancy between different code pages. But I wouldn't want gfxlib2 to be bloated with a hue number of them. BTW, if you use raw console output instead of a graphical mode, then FB can output whatever the native encoding is, e.g. typically UTF-8 on Unix. |
I would like use code page is other than 437 graphical modes. In DOS, I use code page 857. But, FreeBASIC is replace the code page to 437. Is FreeBASIC load internal font on DOS for screen modes? Thanks. |
No, FB does not load system fonts. If you want to display text with the system code page you must use text mode, not a graphical mode (don't call |
I would like to FreeBASIC not use a hardcoded codepage in DOS. FreeBASIC doesn't need to a hardcoded codepage in DOS. |
Hello,
I would like use FreeBASIC. But, FreeBASIC does not support non-English IBM/DOS character sets on graphical screen modes.
I would like to add support non-English IBM/DOS character sets on graphical screen modes?
Thanks.
The text was updated successfully, but these errors were encountered: